• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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