October 16, 2008 at 1:30 pm
Hi
it seems to be some confusion
i have a backup file with size of 6 gb on the disk as it is native back up no compression .
now real confusion comes in place
1. when i restore it on to database the db file size will be 5. 4 some Gb
and log file size will be 27 Gb. that i did not understand where it is coming from
as to save disk space every day i am shrinking log file to 2 gb which is ideal for this case.
so that case i am deletign valid data without saving or what actually happening on there.
2. every time i set the file growth to be restricted for both db and log files.
But after every restore it is being changed to unrestricted . why it is happening .
please put some light me.
thanks in advance.
October 17, 2008 at 7:32 am
Hello Shree,
Though your db backup size is 6 GB it is quite possible that after restore it will grow upto 27 GB.
Find following things:
1. Check source db data and log file size it must be around 27 GB.
2. On source db if extra space is not used; do shrink on data and log.
3. Take fresh(NEW) backup of source db.
4. E.g. after shrink source db size is 8 GB and backup size is 6 GB.
5. Now restore the destination db; this time after restore size will be 8 GB ONLY!!!!
Hope this will help.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
October 17, 2008 at 9:46 am
If your log file is growing from 2Gb to 27Gb every day then there is a reason for it.
Having to shrink the log every day just means SQL has to take time and resources re-growing the log to perform whatever it needs the space for. Take a look for overnight jobs, updates, inserts, index rebuilds and so on.
October 17, 2008 at 10:14 am
If you are shrinking a database or log file every day, you're doing something wrong. As mentioned above you're wasting resources having SQL Server grow it every day.
You want to have free space in the log and data files and rarely, if ever, shrink the files.
October 17, 2008 at 12:30 pm
Your database is apparently in full recovery mode. Make frequent log backup, for example every 2 hours or so.
October 17, 2008 at 12:56 pm
2. every time i set the file growth to be restricted for both db and log files.
But after every restore it is being changed to unrestricted . why it is happening .
please put some light me.
When you restore a database you don't just restore the date, but also its settings.
Like someone else mentioned, if you don't want to use that much disk space shrink the DB files before you back up, indluding the transaction log on the source db (which seems to be the source of the large overall disk space use).
Good luck to you,
~Craig
Craig Outcalt
October 20, 2008 at 8:46 am
Here is my problem always i set Restricted file growth to both Data and Log files.but every day after restore job run it sets backs to unrestricted why ,
how can i control this ,
October 20, 2008 at 2:39 pm
How i can control the file sizes.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply