C
cmm-steve
Guest
Hi,
Thought this might be an issue/bug, sorry if I'm wrong.
After working on a MSSQL Database locally on my development machine, I backed it up using SQL Management Studio and loaded up Plesk, created a new database and selected the "Restore database from backup file". Once this uploaded I noticed it had tried to restore the "sys" user account that is included within the backup from SQLMS.
From what I can find, the sys account included within the backup is non-optional (if I'm wrong could someone fill me in please?). This causes Plesk to report back the warning:
"Some users require your attention. There are several orphaned users that should be repaired in order to function properly."
Plesk provides me with the option to "Repair now" however as this is the 'sys' account it is unable to do so, and because of this I am unable to delete the database from Plesk.
I have gotten around this temporarily by removing the 'sys' account from the Plesk System database (db_users table) using an app I’ve written that is executed via an Event Handler when a new database is created.
If the sys account is non-optional from SQLMS should Plesk not ignore the ‘sys’ account included in any database restores?
Thanks for any feedback.
-Steve
Thought this might be an issue/bug, sorry if I'm wrong.
After working on a MSSQL Database locally on my development machine, I backed it up using SQL Management Studio and loaded up Plesk, created a new database and selected the "Restore database from backup file". Once this uploaded I noticed it had tried to restore the "sys" user account that is included within the backup from SQLMS.
From what I can find, the sys account included within the backup is non-optional (if I'm wrong could someone fill me in please?). This causes Plesk to report back the warning:
"Some users require your attention. There are several orphaned users that should be repaired in order to function properly."
Plesk provides me with the option to "Repair now" however as this is the 'sys' account it is unable to do so, and because of this I am unable to delete the database from Plesk.
I have gotten around this temporarily by removing the 'sys' account from the Plesk System database (db_users table) using an app I’ve written that is executed via an Event Handler when a new database is created.
If the sys account is non-optional from SQLMS should Plesk not ignore the ‘sys’ account included in any database restores?
Thanks for any feedback.
-Steve