In the final step, you can choose to:
Upsize
Select to begin creating databases and tables, as applicable, on the remote server.
Save generated SQL
Select to have the upsizing wizard generate the SQL script necessary to upsize your database and then stop without beginning to create databases and tables on your remote server.
You can use this option to provide a SQL upsizing script that you then customize to meet the needs of your application. Once you've modified and saved the SQL script, you then run the script to complete the upsizing process. This two-step process provides tremendous flexibility, allowing you to use Visual FoxPro to generate the large majority of the code you'll need, yet providing a method for fine-tuning the upsized installation.
Upsize and save generate SQL
Select to upsize your database and save the SQL script generated by the wizard.
To upsize your database
The SQL Server Upsizing Wizard creates devices and databases if necessary, and begins exporting Visual FoxPro objects to SQL Server.
The first and third upsizing options are available only if you have CREATE TABLE permission on the server. If you choose either of the options that save generated SQL code, all the SQL code generated by the SQL Server Upsizing Wizard is stored on your hard disk.
Note Upsizing can take a long time, depending on the size of your data, the amount of network traffic, and the number of concurrent demands being handled by your server. Large tables can require several hours to export.
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.
The SQL Server Upsizing 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
-or-
To increase the space for an existing database
To increase the space for an existing log
-or-
Dump the transaction log.
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.
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
Caution 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.