Microsoft KB Archive/162372

= UT95: Upsizing Wizard Fails When Out of Disk Space on SQL Server =

Article ID: 162372

Article Last Modified on 11/12/2000

-

APPLIES TO


 * Microsoft Access 95 Upsizing Tools

-



This article was previously published under Q162372



Advanced: Requires expert coding, interoperability, and multiuser skills.



SYMPTOMS
When you use the Upsizing Wizard for Microsoft Access 7.0 to export a database to SQL Server, you may receive the following error message:

Server Error 1105: Can't allocate space for object 'Syslogs' in database 'SQLCleanWind' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.



CAUSE
The Upsizing Wizard does not check the SQL Server to see if there is enough available disk space on the server, nor does it check the amount of available space for the transaction log before it tries to upsize a database to SQL Server. If the Upsizing wizard does not have enough disk space on the server to paste the database or if it does not have enough space for the transaction log, it will fail.



RESOLUTION
If the Upsizing Wizard fails, do one or more of the following:
 * Free up a sufficient amount of disk space on the SQL Server.
 * Increase the amount of space available for the transaction log.
 * Dump the transaction log.



STATUS
Microsoft has confirmed this to be a problem in Microsoft Access 7.0. This problem no longer occurs in Microsoft Access 97.



MORE INFORMATION
The Upsizing Wizard takes a Microsoft Access database and creates a database on SQL Server with the same table structure, data, and many other attributes of the original Microsoft Access database. Before you upsize a database to SQL Server, you must check to see if the server has sufficient disk space. If the server does not have enough disk space, you will need to increase the space for a new database or log.

NOTE: If the Upsizing Wizard does fail, it will leave an empty table on the server. This table should be deleted before you try to upsize your database again.

