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

« Previous Version 12 Next »

By default, the Connexion installer will perform the following database operations that require sysadmin access to the database server:

  1. Creates 2 databases: A configuration database (2 file groups: PRIMARY, LOG), and a message database (3 file groups: PRIMARY, INDEX, LOG) 
  2. Creates a  database user and assign the user as db_owner to the databases created in (1) 
  3. Enables .net on the Sql Server instance: EXEC sp_configure 'clr enabled', 1;
  4. Installs an optional .NET assembly and function used for searching text within a message. (If this function is not available, searching for data within a message will fail)
  5. Installs an optional view that provides decompressed message data

In some cases it is not possible to install Connexion using a user with 'sysadmin' privileges. Under this condition, the following manual steps must be performed to configure Connexion:

  • Manually create the configuration database. The database name must start with 'CXN_' (default is CXN_Connexion):

  • Manually create the message database.

(a) The database name should be the name of the configuration database with '_Default' appended. For example, 'CXN_Connexion_Default'.

(b) You must add an index filegroup named exactly 'INDEX'

  • Create / edit your installer user. This is the user you will use to run the Configuration Wizard (this wizard configures/upgrades Connexion and the various databases). This user should have db_owner permissions on the two databases you've created. 

  • Create / edit your service user. This is the user you will use to run the Configuration service. This user should have reader/writer permissions on the two databases you've created.



  • Now run the Configuration wizard using an account that has (at minimum):


    1. DBO permissions on the database (in order to create tables, edit schemas etc.)

    2. Local administrator rights (in order to manage local folders, services, certificates, etc.)

You may need to use the 'runas' functionality from a command line in order to impersonate a user which has these required privileges:

Command Prompt
runas /user:MyUser ConfigurationWizard.exe

Please ensure that on the connections tab of the configuration wizard you have checked the 'Skip Sql Server sysadmin operations...'





  • No labels