SQL Server Gurus: SQL Server DB Restore gives this error: System.Data.SqlClient.SqlError: There is insufficient free space on disk volume 'C:\' to create the database. The database requires 210068836352 additional free bytes, while only 209935310848 bytes are available. (Microsoft.SqlServer.Smo) I understand the backup file is 121mb and the thing says it requires 195GB to restore. How 195 gig can be compressed into 121mb is beyond me so lets not go there. Question: How can we resolve this? Google suggests shrink the log first (which is the main culprit coz its demanding the 195gb). Shida ni its a backup. I dont think its possible to shrink a log file in a backup file (correction welcome) If the original was available it would be easy to shrink the log file BEFORE taking the backup. Am not physically at the site but I can relay the responses you guys give. Thanx in advance
Lawi, The person on site should have done the truncation before doing the backup. You can use this script to do the truncation of the logs; BACKUP LOG [DATABASE_NAME] WITH TRUNCATE_ONLY DBCC SHRINKDATABASE ( [DATABASE_NAME] , TRUNCATEONLY ) Only alternative is for the user to get the hard disk space requested for so that the restoration can be done. Then carry out truncation after restoring. Kind regards, Kevin On Thu, Sep 16, 2010 at 11:55 AM, Mr. Lawi <mail2lawi@gmail.com> wrote:
SQL Server Gurus:
SQL Server DB Restore gives this error:
System.Data.SqlClient.SqlError: There is insufficient free space on disk volume 'C:\' to create the database. The database requires 210068836352 additional free bytes, while only 209935310848 bytes are available. (Microsoft.SqlServer.Smo)
I understand the backup file is 121mb and the thing says it requires 195GB to restore. How 195 gig can be compressed into 121mb is beyond me so lets not go there.
Question: How can we resolve this?
Google suggests shrink the log first (which is the main culprit coz its demanding the 195gb). Shida ni its a backup. I dont think its possible to shrink a log file in a backup file (correction welcome)
If the original was available it would be easy to shrink the log file BEFORE taking the backup.
Am not physically at the site but I can relay the responses you guys give.
Thanx in advance
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Server donations spreadsheet
http://spreadsheets.google.com/ccc?key=0AopdHkqSqKL-dHlQVTMxU1VBdU1BSWJxdy1f... ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
Greetings Lawi, From your comments, the issue is the free space size on Drive C. I would recommend that if the machine on which you want to do the backup is partitioned into other drives, you could create the Database on the other Drive that has more space by specifying the location. As you had also said, one way of avoiding this is to shrink the log files before doing a backup. That would really help a lot. On Thu, Sep 16, 2010 at 1:55 PM, Mr. Lawi <mail2lawi@gmail.com> wrote:
SQL Server Gurus:
SQL Server DB Restore gives this error:
System.Data.SqlClient.SqlError: There is insufficient free space on disk volume 'C:\' to create the database. The database requires 210068836352 additional free bytes, while only 209935310848 bytes are available. (Microsoft.SqlServer.Smo)
I understand the backup file is 121mb and the thing says it requires 195GB to restore. How 195 gig can be compressed into 121mb is beyond me so lets not go there.
Question: How can we resolve this?
Google suggests shrink the log first (which is the main culprit coz its demanding the 195gb). Shida ni its a backup. I dont think its possible to shrink a log file in a backup file (correction welcome)
If the original was available it would be easy to shrink the log file BEFORE taking the backup.
Am not physically at the site but I can relay the responses you guys give.
Thanx in advance
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Server donations spreadsheet
http://spreadsheets.google.com/ccc?key=0AopdHkqSqKL-dHlQVTMxU1VBdU1BSWJxdy1f... ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
C has 195 gb free. The DB itself (from earlier backups) is less than 1gb in size. Right now my suspicion is on the backup file. Anyway, we are tryin to restore the data only (minus the log). I will share what happens. One other thing: The original db was nowhere near 195gb at the time the backup was taken. How is it that now the restore claims to require 195gb? Anyway, thanx for your responses. Point noted: Shrink before backup. Shrink before backup. Shrink before backup. Shrink before backup. ... On Thu, Sep 16, 2010 at 2:28 PM, Emmanuel Ochieng < emmanuelochieng797@gmail.com> wrote:
Greetings Lawi,
From your comments, the issue is the free space size on Drive C. I would recommend that if the machine on which you want to do the backup is partitioned into other drives, you could create the Database on the other Drive that has more space by specifying the location.
As you had also said, one way of avoiding this is to shrink the log files before doing a backup. That would really help a lot.
On Thu, Sep 16, 2010 at 1:55 PM, Mr. Lawi <mail2lawi@gmail.com> wrote:
SQL Server Gurus:
SQL Server DB Restore gives this error:
System.Data.SqlClient.SqlError: There is insufficient free space on disk volume 'C:\' to create the database. The database requires 210068836352 additional free bytes, while only 209935310848 bytes are available. (Microsoft.SqlServer.Smo)
I understand the backup file is 121mb and the thing says it requires 195GB to restore. How 195 gig can be compressed into 121mb is beyond me so lets not go there.
Question: How can we resolve this?
Google suggests shrink the log first (which is the main culprit coz its demanding the 195gb). Shida ni its a backup. I dont think its possible to shrink a log file in a backup file (correction welcome)
If the original was available it would be easy to shrink the log file BEFORE taking the backup.
Am not physically at the site but I can relay the responses you guys give.
Thanx in advance
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Server donations spreadsheet
http://spreadsheets.google.com/ccc?key=0AopdHkqSqKL-dHlQVTMxU1VBdU1BSWJxdy1f... ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Server donations spreadsheet
http://spreadsheets.google.com/ccc?key=0AopdHkqSqKL-dHlQVTMxU1VBdU1BSWJxdy1f... ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
participants (3)
-
Emmanuel Ochieng -
Kevin Oeba -
Mr. Lawi