• 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.

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