06-20-2007 10:18 AM
06-20-2007 04:19 PM
06-20-2007 04:36 PM
Tip
If you put multiple batch files in the same MS-SQL-Server policy, they will executeduring each Automatic Backup session for that MS-SQL-Server policy. If you have a
variety of SQL Server backup operations that you wish to have executed on
different schedules, then consider creating multiple MS-SQL-Server policies with
differing Automatic Backup schedules; and then assign each batch file to the policy
that uses the desired Automatic Backup schedule.
06-21-2007 06:33 AM
06-21-2007 09:35 AM
OBJECTTYPE DATABASE
DATABASE "Test_Database"
NBIMAGE "<hostname>.MSSQL7.<HOSTNAME>.db.Test_Database.~.7.001of001.20070621104847..C"
DUMPOPTION INCREMENTAL
DATABASE "Test_Database"
NBIMAGE "<hostname>.MSSQL7.<HOSTNAME>.inc.Test_Database.~.7.001of001.20070621111538..C"
I would assume it'd be a bit of work but point me in the right direction and I'll go from there. I assume if I can find NBIMAGE via one of the commands I should be able to put together the batch files on the fly. That's pretty much what we want to do with the exception of the database name since that's set in the create/populate script as well as the modification scripts I have already working fine.
Thanks in advance, this is something that I need to get functional by next week so the pressure is on my end ;)
Mike