• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Cannot Drop Database when calling Entity Framework DropDatabaseAlways Initializer

WebDBApps

New Pleskian
I've deployed an Asp.net MVC application to Plesk 12.5 running on Windows Server 2012 with SQL Server 2014. The database was already created through Plesk and a service account was assigned to it.

In testing the app, I'm calling the Entity Framework Seed method to initialize the database with an admin user. This method, for now, calls DropDatabaseAlways in my initializer. When I attempt to login, the message stating cannot drop database is thrown. Can the Plesk service account be given dbo privilege on the database? I did not see this in the Plesk database screens and am unsure if I can elevate the permissions in Management Studio.

How can I modify my server environment to allow for this database initialization? Thanks for your help and guidance.
 
Back
Top