• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

MSSQL: Add existing DB to Plesk

S

sdm-cs

Guest
Hi all,

I've been using Plesk 7.5 for Windows for a few months now, it's been great! However I now have the following problem, I really hope you can help me! :)

One of our developers migrated one of our busiest web sites onto our Plesk web server but did not create the MSSQL database through Plesk, instead he just loaded a backup directly into Enterprise Manager which means Plesk doesn't have a clue it exists. I've tried creating it through Plesk web admin and it fails each time because the database already exists within MSSQL.

I think that reads Ok, so if you have any idea how I get this database recognised by Plesk, that would be smashing, thanks!
 
Originally posted by sshigin
before create domains via Plesk and then restore databases over
I actually tried the following shortly after posting this (it worked!):
  • Detached the database in Enterprise Manager
  • Renamed the two files in the MSSQL data folder
  • Created the database in Plesk web admin
  • Detached the new database created by Plesk in Enterprise Manager
  • Removed those files from the MSSQL data folder
  • Named the original data files back to their original name
  • Attached the files to the database in Enterprise Manager
  • Created a user account for this database within Plesk web admin
I think that's all I did, and it seems to be running fine now.

Thanks! :)
 
Back
Top