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 |
Chetan_JMM
Starting Member
4 Posts |
Posted - 2006-11-30 : 00:15:06
|
Hi Group,I am facing problem while database restoration.My database size is 38 GB and backup file size is 6 GB. (database is having very free space but i dont have rights to do shirnk the database).My Machine has two HDD. First has free space of 33 GB and second one has free space of 10 GB.While doing restore from enterprise manager, it is giving me error of insufficient space in C drive.Can anybody help me out in this.Regards,Chetan |
|
monty
Posting Yak Master
130 Posts |
Posted - 2006-11-30 : 01:31:18
|
1)what is the size of log?2)do u take regular transactional logs?3)is point in time recovery must?4)to which drive you are trying to restore, the one which has 33GB or the 10 GB one.5)its not a gud method to restore from EM though.. also please paste the complete error message...its me monty |
 |
|
monty
Posting Yak Master
130 Posts |
Posted - 2006-11-30 : 01:34:45
|
quote:
2)do u take regular transactional logs? quote:
i meant transactional log backup's its me monty |
 |
|
Chetan_JMM
Starting Member
4 Posts |
Posted - 2006-11-30 : 01:41:08
|
1) what is the size of log? --- 10 GB2)do u take regular transactional logs? --- No3)is point in time recovery must? --- No, it is normal database restoration.4)to which drive you are trying to restore, the one which has 33GB or the 10 GB one. -- the one which has 33 GB5)its not a gud method to restore from EM though.. --- Can u suggest me other way.also please paste the complete error message... --- It is showing insufficient disk space msg. |
 |
|
Kristen
Test
22859 Posts |
Posted - 2006-11-30 : 01:50:41
|
If you make a backup from a 33GB database the first thing the restore will do is create a 33GB file. Even though there was only 6GB of "data" in the original database.The normal way around this is to first shrink the source database, then back it up, then restore it to the target server.If you have another SQL Server lying around with 33GB spare you could restore there, shrink, backup, and then restore that backup locally (and DROP the database from the "spare server")An alternative might be to Script the source database, create a new database on the target server, and then transfer the data (with DTS, BCP or somesuch).Kristen |
 |
|
monty
Posting Yak Master
130 Posts |
Posted - 2006-11-30 : 01:59:55
|
quote:
If you make a backup from a 33GB database the first thing the restore will do is create a 33GB file. Even though there was only 6GB of "data" in the original database quote:
i suppsose it is 38 GB database rather than 33GB i guess its a typo mistake kristenyes it will create a 38 GB file on restore hence as you are having only 33 GB free space left you are getting this error. quote:
database is having very free space but i dont have rights to do shirnk the database). quote:
as you dont have rights to shrink it you need either to add disks or follow the methods told by kristenits me monty |
 |
|
Chetan_JMM
Starting Member
4 Posts |
Posted - 2006-11-30 : 02:08:55
|
Does any body knows how to restore database from query analyzer with shirinking the database.If this will workout, then my problem is solved.@Kirstan, First -- I don't have rights to shirnk the database.Second -- Even i don't have other box which i can use for restore purpose.Third -- that is advisable, but i have lots of tables which will be difficult to export with dtp /bcp |
 |
|
|
|
|
|
|