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.

How to Change the SQL Server Instance

  • Last updated on

This article applies to PST Enterprise version 3.1 or higher.

You can change the SQL instance used by PST Enterprise. For example, if you have reached the maximum database size limit for SQL Express instances and wish to migrate to a full SQL server instance.

To change the SQL Server instance,

  1. Confirm your PST Enterprise system configuration.
  2. Confirm you have a copy of the PST Enterprise installer which is needed to reinstall PST Enterprise. If you do not have a copy, contact Barracuda Support.
  3. On the PST Enterprise server, stop the PSTEnterprise and PSTEnterpriseSelfService websites in Internet Information Services (IIS) Manager to prevent clients from connecting during the SQL database migration.
  4. (Optional but recommended). Migrate the PST Enterprise database (PSTEnterprise) to the new SQL instance. For migration options, refer to the Microsoft blog Nice things inside SQL Server, System Center Configuration Manager.
    • The database name must be PSTEnterprise.
    • If you do not migrate the database, all your previous configuration (discovered PSTs, client configuration, policies, etc.) are lost. You must reapply this configuration once PST Enterprise is configured to use the new SQL instance.
    • Verify the PST Enterprise Admin account has the required SQL database permissions.
  5. Once the SQL database is migrated, uninstall PST Enterprise from the Control Panel.
  6. Reinstall PST Enterprise.
  7. Once reinstalled, start the PSTEnterprise and PSTEnterpriseSelfService websites in IIS Manager. Clients can now reconnect and continue processing.

PST Enterprise is now configured to use the new SQL instance.

Last updated on