• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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