How to: Resolve SQL Server Upsizing Wizard Errors
If any errors occur while the SQL Server Upsizing wizard is exporting data, you are asked whether you want to save error information. If you choose to save error information, an error report is generated.
Most upsizing errors occur because there isn't enough space on your server's database or log device, or because your remote database is not large enough to accept the data you're exporting to the server. Make sure that you select devices with ample free space and that you set your database size sufficiently high. Some errors occur because of inappropriate login permissions.
Database or Log Full
The SQL ServerUpsizing wizard runs out of space and stops if the SQL database you selected or created is too small. To resolve this problem, you can increase the space for the database or the log. This solution can involve dropping (removing) the database or the log from the upsizing process.
To increase the space for a new database or log
Drop the database.
If the SQL Server Upsizing wizard changed the names of any local tables, restore tables to their original names by:
Copying your backup version of your local database's .dbc file onto your system, overwriting the altered .dbc file.
-or-
Renaming local tables to their original names.
When you run the wizard again, specify a larger database or log size.
To increase the space for an existing database
Increase the size of the database.
If the SQL Server Upsizing wizard changed the names of any local tables, rename them to their original names.
Copying your backup version of your local database's .dbc file onto your system, overwriting the altered .dbc file.
-or-
Renaming local tables to their original names.
Run the wizard again.
To increase the space for an existing log
Increase the size of the log.
-or-
Dump the transaction log.
If the SQL Server Upsizing wizard changed the names of any local tables, rename them with their original names.
Copying your backup version of your local database's .dbc file onto your system, overwriting the altered .dbc file.
-or-
Renaming local tables to their original names.
Run the wizard again.
You should overwrite tables from the previous partial upsizing to make sure all table relationships are created.
For information on increasing the database or log size, see the ALTER DATABASE command in your SQL Server documentation. For information on dumping the transaction log, see the DUMP TRANSACTION command in your SQL Server documentation.
Device Full
The device on which a database or log is located can fill up. You can extend the database or log to another device using the ALTER DATABASE command or the SQL Server Administrator, or you can create a larger device.
To create a larger device
Drop the device.
Restart SQL Server.
Create a larger device.
Warning
Dropping a device deletes all databases and logs on the device, not just the database to which you are upsizing.
You can use the sp_dropdevice system procedure to drop a device. For more information, see your SQL Server documentation.
Improper Compatibility Level for Upsizing
To upsize a database, Visual FoxPro sets the compatibility level of the target SQL database to 6.5 by calling the SP_DBCMPTLEVEL stored procedure on SQL Server. Make sure the SQL login you are using has the appropriate rights to perform this action.
To make sure the SQL login has appropriate rights
Verify that the login you are using has the permissions as one of the following:
DBO
Member of the sysadmin fixed server role
DB_OWNER fixed database role
See Also
Concepts
How the SQL Server Upsizing Wizard Works