Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
thecoffeeguy
Yak Posting Veteran
98 Posts |
Posted - 2007-01-23 : 18:28:36
|
Basically, trying to restore one database from one server to another database server, so we can have two copies of the database.Here is what i did:I took a full backup of the database we wanted to restore on the other server. I copied the .bak file to the second server and then tried to run the following script:RESTORE DATABASE siebeldbFROM DISK='C:\Documents and Settings\Administrator\Desktop\011907full.bak'WITH MOVE 'siebelprddb_Data'TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\siebeldb_Data.mdf',MOVE 'siebelprddb_Log'TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\siebeldb_Log.mdf',REPLACE Problem is, I get this error code:Server: Msg 3257, Level 16, State 1, Line 1There is insufficient free space on disk volume 'C:\' to create the database. The database requires 56168415232 additional free bytes, while only 50647908352 bytes are available.Server: Msg 3013, Level 16, State 1, Line 1RESTORE DATABASE is terminating abnormally.Which is weird, because the "C:" has about 47gigs of free disk space and the backup file is only 16gigs.Any ideas? I'm lost. |
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2007-01-23 : 18:45:50
|
The dtabase will be restored to the size of the original database. Sounds like there was about 16 Gb of data but the data file and tr log were 56 GB. Check the source database and see if the tr log has grown - if so shrink it before the backup - otherwise shrink the data fle.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
thecoffeeguy
Yak Posting Veteran
98 Posts |
Posted - 2007-01-23 : 18:49:23
|
quote: Originally posted by nr The dtabase will be restored to the size of the original database. Sounds like there was about 16 Gb of data but the data file and tr log were 56 GB. Check the source database and see if the tr log has grown - if so shrink it before the backup - otherwise shrink the data fle.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy.
that would make sense because I believe the tlog file is 37gigs, but needs to be shrunk.probably just shrink it to 1gb, that should do it?Long story, but that should be sufficient right now. |
 |
|
thecoffeeguy
Yak Posting Veteran
98 Posts |
Posted - 2007-01-23 : 18:55:12
|
anyone have any idea how long it would take to shrink a 37gig tlog file to 1gig?4 CPU box, with 4gigs RAM and 15,000 RPM SCSI Disks. |
 |
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2007-01-24 : 04:20:30
|
Shouldn't take long as you aern't moving data just releasing space.I would expect a couple of minutes max.If you use the gui make sure you shrink the log file and not the database and just release unused space.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
|