We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

SQL Database Permissions

  • Last updated on

This article applies to the Barracuda PST Enterprise version 3.1 or higher.

During installation of PST Enterprise you can, optionally, choose to install a managed version of SQL Server 2008 R2 Express. If you select this option then the PST Enterprise Admin account (by default named PSTEnterpriseAdmin) is automatically given the sysadmin role in the SQL instance that is installed.

If you want to make use of an existing SQL Server instance, it is recommended that the PST Enterprise Admin account be given either the sysadmin role or that the PSTEnterprise database be pre-created (the database must be named PSTEnterprise) and the PST Enterprise Admin account given the dbcreator role to that pre-created database. This allows PST Enterprise to verify whether the required database exists by attempting to create it. If the database creation fails because the named database already exists, then PST Enterprise automatically creates any necessary tables, views, sprocs, etc. that do not already exist. Merely being a dbowner of the PSTEnterprise database does not give the PST Enterprise Admin account sufficient permissions to do this, even if the database already exists.

 

Last updated on