Detailed analysis: difficult issues during SQL database Conversion

This article will briefly explain some difficult issues related to SQL database conversion. You can make a reference in practical use ...... Possible causes: ◆ the source database or target database is SQLServer6.5. The current SQL Server connecting to the Access Project and the target server to convert the database to must be SQLSe

This article will briefly explain some difficult issues related to SQL database conversion. You can make a reference in practical use ...... Possible causes: ◆ the source database or target database is SQL Server 6.5. The current SQL server connected to the Access Project and the target server to convert the database to must be SQL Se

This article will briefly explainConvert SQL databaseFor some difficult issues, you can make a reference in practical use ......

Possible causes include:

◆ The source database or target database is SQL Server 6.5. The current SQL Server connecting to the Access Project and the target Server to which the database is to be converted must be SQL Server 7.0 or later.

◆ You must be a member of the sysadmin role on the target server. Although you are not a member of the sysadmin role on the source Server, you must be a member of the sysadmin role on the target Server to switch to the SQL Server database.

◆ A database with the same name already exists on the target server. Provide a new name for the database.

◆ Insufficient disk space. If there is not enough disk space to create a new database, Access will cancel the database conversion operation.

Make sure that there is sufficient disk space on the target server before performing the database conversion operation.

If an error occurs during database conversion, open the conversion log file created in the same folder as the Access Project to view details.

The extended attributes are not copied during SQL Server database conversion.

To copy extension properties, Access requires Microsoft Data Access Components (MDAC) 2.6 to be installed on the local computer. If SQL Server 2000 or SQL Server 2000 Desktop Engine is not installed on the local computer, you can only have MDAC 2.5.

To install MDAC 2.6, install the SQL Server 2003 Desktop Engine on your local computer from the \ MSDE2000 folder of the Microsoft Office 2000 CD-ROM.