• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue SQL import is changing name of the .mdf file for the existing database

Harvey64

New Pleskian
When exporting a database with Plesk and then importing it to a new database, for some reason the .mdf and log file names for the new database are being changed. For example:

1) I created two empty databases .... test_db and test_db2.
2) I confirmed that the following two .mdf files were created:

C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\test_db
C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\test_db2

3) I exported the test_db using Plesk.
4) I then imported that file to the test_db2 database and found that the name of the mdf file for the test_db2 changed to the following:

C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\test_db2_test_db_3e7101bb90b04fc9a84c431d386beba4

---------------------------------------------

Why is this happening, is there a setting somewhere that can change this behavior?

NOTE: I fully understand that there is a "copy" option within Plesk which can be used to accomplish the same thing without modifying mdf file names, but in some cases when a database contains fields with large amounts of data the "copy" (or clone) option fails to work.

Thanks!
 
Back
Top