The database names imported from SQL Server to the virtual host virtual space are inconsistent.

The SQL Server data import of the VM Virtual space has been troublesome. So far, no virtual space can be directly restored to the database backup on FTP. If yes, we recommend it. Generally, we use the data import and export method to import a local database to a virtual space. Of course, the defect of import and export is that the primary key, default value, and automatic growth will be lost. Therefore, to maintain consistency with the local database, we generally export the SQL statement first, execute the SQL statement in the SQL query of the virtual space, generate the table structure, and then use the Import and Export function, import data. However, we recently found that sqlserver consistently prompts "** table already exists" error during data import. After some searches, we found that the original data name of the local machine was Magezine, and the remote data was International. The database names were inconsistent, so that SQL automatically created the target table for you. Delete the local data, re-create the same database name as the remote database, restore the database, and then import and export the data to import the data correctly!