January 30, 2009 at 9:41 pm
Hi everybody!
A database at work used to have ~ 7 GB and its restore time from a full backup was ~ 5-6 minutes. After adding a few tables, the size of that DB went to ~ 8.5 GB (the size of data file, the log size is ~ 5 GB). Now the restore time from the same type of backup is ~ 40 minutes.
The backup file is located on a local drive (server), it is not saved in a remote location, the server load hasn't changed, in my opinion it is a space issue - the first location (OS) has ~ 1.5 GB free space, the second (SQL Server 2000 installed on it, tempdb is here) has ~ 6 GB free, the third and the fourth (with the DB and the backup files) have both plenty of free space (~ 30 GB each of them).
If important, DB has auto-grow enabled (but it had it enabled before too).
What can I do here to improve this? What physical resources (others than writing the data file and the log file) are used during a restore from a full backup?
January 30, 2009 at 11:55 pm
Can you try a restore from one of the older backups? One from before you added the new tables. That may help narrow down the problem.
February 3, 2009 at 5:23 pm
Can you post the output of restore filelistonly from disk='complete backupfilepath.bak'?
MJ
February 4, 2009 at 10:04 am
This is the content of the last daily backup :
LogicalNamePhysicalName TypeFileGroupNameSize MaxSize
xyz_DataE:\amddbs\xyz_Data.MDF D PRIMARY 868935270435184372080640
xyz_Log F:\amsdblogs\xyz_Log.LDFL NULL 574003609635184372080640
Unfortunately, I don't have the older backups ...
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply