September 15, 2011 at 4:27 am
I strongly, strongly recommend that you do not back everything up to the same backup file - put in a timestamp as part of your backup name and have a new file for each backup. I'd advise checking out Ola Hallengren's excellent scripts rather than try to re-invent the wheel:
Nothing "has priority", it's all a matter of timing in terms of which schedule gets there first and there's no magic fix other than make sure the schedules don't conflict with each other
September 15, 2011 at 4:31 am
Ok cool, thanks. So best is then that I create different backup devices for:
1. Full backup
2. Differential backup
3. T-Log backup
I will check it the link you posted
September 15, 2011 at 4:39 am
The link posted above contains an extremely useful set of scripts suitable for regular maintainance.
However, since you are trying to learn things, you should write your own scripts and practise.
Also, as rightly pointed out, keep all backups in separate files. A good way to do is append timestamp at the end of the file name.
something like
'myserver_mydb_full_'+convert(varchar,getdate(),112)+'.bak'
September 15, 2011 at 4:41 am
pierrelessing (9/15/2011)
Ok cool, thanks. So best is then that I create different backup devices for:1. Full backup
2. Differential backup
3. T-Log backup
No. Ignore backup devices and write each backup to its own file. Far easier to find when you need them.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply