Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Current »

Versions Supported

Connexion will run on Sql Server 2008R2, 2012, and 2014, including the express versions of these databases.

Database Types

Connexion uses 2 different types of databases: a single configuration database, and 1, or more message storage databases. The server and database management screen is shown in Figure 1. The configuration database is the labeled "Active", and the 2 message databases are labeled "Default" and "LongRunning".

Within Sql Management Studio these databases appear as shown in figure below. There are a few additional things to note about these databases:

  1. All Connexion databases are prefixed with CXN_.
  2. The name of the main Connexion configuration database is set during installation time as shown in Figure 2
  3. Each message storage database is prefixed with the name of the main configuration database to which it belongs. This was done to allow users, and scripting tools to easily identify which databases belong to a particular instance of Connexion.
  4. Multiple instances of Connexion can be hosted by a single Sql Server instance. As shown in the Sql Management UI below, there are 2 instances of Connexion: CXN_Connexion, and CXN_Connexion2.

Figure 1

Server and Database Management Screen

Figure 2

Setting Connexion Configuration Database name

Database Maintenance

Connexion has been designed to automatically perform the necessary database maintenance tasks to maintain the performance and integrity of the system. This includes database backup, purging of old records from the database, index maintenance, and database integrity checks.

The database maintenance settings can be found by clicking on the main Connexion configuration database, or one of the message databases (see Figure 1).

Each of the automated database maintenance routines can be disabled for those customers that wish to manage the maintenance outside of Connexion.


 

Database Permissions

Connexion uses and excellent set of open source scripts to perform the nightly database maintenance routines. The details of these routines can be found on the author's website here: https://ola.hallengren.com

These scripts require the following database permissions to execute (see https://ola.hallengren.com/frequently-asked-questions.html)

  • DatabaseBackup: sysadmin
  • DatabaseIntegrityCheck: EXECUTE on dbo.DatabaseIntegrityCheck, VIEW DEFINITION on dbo.CommandExecute, VIEW DEFINITION on dbo.CommandLog, VIEW SERVER STATE, db_owner on all target databases
  • IndexOptimize: EXECUTE on dbo.IndexOptimize, VIEW DEFINITION on dbo.CommandExecute, VIEW DEFINITION on dbo.CommandLog, VIEW SERVER STATE, db_owner on all target databases

These options are explained in more detail below.

Database Backup

 

 

 

To perform these tasks, Connexion requires the following database permissions.

  • DatabaseBackup: sysadmin
  • DatabaseIntegrityCheck: EXECUTE on dbo.DatabaseIntegrityCheck, VIEW DEFINITION on dbo.CommandExecute, VIEW DEFINITION on dbo.CommandLog, VIEW SERVER STATE, db_owner on all target databases
  • IndexOptimize: EXECUTE on dbo.IndexOptimize, VIEW DEFINITION on dbo.CommandExecute, VIEW DEFINITION on dbo.CommandLog, VIEW SERVER STATE, db_owner on all target databases.


  • No labels