BUG: Restore of a Large Database on Windows 98 May Fail with 3257 Error Message (273833)
The information in this article applies to:
- Microsoft SQL Server 7.0
- Microsoft SQL Server 2000 Desktop Engine (MSDE)
- Microsoft SQL Server 2000 Personal Edition
This article was previously published under Q273833
BUG #: 58340 (SQLBUG_70)
BUG #: 236139 (SHILOH_BUGS)
SYMPTOMS
Restoring a database backup on Microsoft Windows 98 fails if all the following conditions are met:
- The file size of the restored database is 2 GB or greater.
- The database is being restored over an existing database that is less than 2 GB even if there is more than 2 GBs of free disk space.
Here is an example of the error message that might occur:
Server: Msg 3257, Level 16, State 1, Line 1
There is insufficient free space on disk volume 'D:\MSSQL7\DATA' to create the database. The database requires 2352873472 additional free bytes, while only 2147155968 bytes are available.
Server: Msg 3013, Level 16, State 1, Line 1
Backup or restore operation terminating abnormally.
This error message occurred while attempting to restore a 2 GB database over a newly created or existing database that was less than 2 GB. The restored database file (.mdf) would have been 2,352,873,472 bytes in size.
CAUSE
On Microsoft Windows 98, a different Win32 function is called to determine how much free space is available. The function that is called returns a maximum of 2 GB free space. For additional information about the Win32 function, click the article number below
to view the article in the Microsoft Knowledge Base:
231497 INF : Understanding and Using GetDiskFreeSpace and GetDiskFreeSpaceEx
WORKAROUND
To work around this behavior, you can use either of the following methods:
- Create a database that is approximately the same size of the database from which the backup was created and then restore over the newly created database.
-or-
- Turn on trace flag 3104 and then restore the database. Trace flag 3104 causes SQL Server to bypass checking for free space.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 11/14/2003 |
---|
Keywords: | kbBug kbpending KB273833 |
---|
|