October 26, 2011 at 1:02 pm
Hello Everyone
i like to know about the use of files in a database and make partial backups, is true than i can make some files read only and all the database began to grow only in certain file? so i can make less backup from the read only files and everydaybackup from the only file than stills grow up??
please give me some feedback about this idea, i have several historical database with + 10GB and little grow up of data...
please help
October 26, 2011 at 1:05 pm
Maybe the best way to handle this is to put your read only tables in one or more filegroups that are separate from your read/write tables. Then you can specify that only certain filegroups should get backed up. This makes sense if you have large read-only tables that you can reload from a file or other source, so it's not necessary to back it up every night.
October 26, 2011 at 1:08 pm
10GB is tiny, far below where one would normally start with partial backups and piecemeal restores.
Yes, you can do what you say, however make very, very, very sure you understand the complexities of file/filegroup backups and piecemeal restores before you start.
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
October 26, 2011 at 3:09 pm
Might be easier to do full backup weekly and the log backup after each load.
For the same 50 GB 1 give you 5 days while the other one possibly gives you 5 months of backups.
Of course if only 1 log backups breaks you're 100% screwed at that point.
As Gail said, 10 GB is absolutely nothing. A 1 000 GB drives costs less than 100$ these days so unless you want to do this for practice I'd just keep doing full backups.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply