June 2, 2008 at 3:04 pm
Hi
I've tried and tried to figure this out with much searching but to no avail, so now i have to ask... i am using sql 2005 Express and i have a .sql script to automate my backup daily - it looks like this:
BACKUP DATABASE [db_name] TO DISK = N'C:\path_to\db_nam.bak' WITH NOFORMAT, NOINIT, NAME = N'db_name-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10
GO
According to properties of the db in management studio express, the actual db is only 157mb, but the .bak file this script is generating is 3GB!!! there is no single directory on this whole pc, in the \sql folders or anywhere else, that contains this much data.... so i can't figure out for the life of me why the heck my .bak is soooo big? Is it the logs?
Some potentially useful data - another employee added A LOT of data to the database, then deleted it in several attempts to properly import some csv files from an another outdated program - i have the feeling that somehow the Sql Server Logs may be causing the excessive size from all this activity...? i noticed that right-click-the-db/properties/file/autogrowth .ldf file setting is at (the default i suppose) limit of 2097152mb - could this be my issue? If so, is there harm in knocking this size way down?
Any help is very, very much appreciated - thanks!!!
mike
June 2, 2008 at 3:27 pm
You are using NOINIT, which means you append each day's backup to the file.
Use INIT to create a new file each day.
June 2, 2008 at 3:56 pm
Steve:
Thanks a bunch... therein lies the problem with no quite knowing enuf about the details in the script... my bad. :ermm:
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply