Migrating Enterprise Tester from one server to another

As your ET instance grows it may be necessary to upgrade your server. This article takes you through the steps required when moving to a new server.

About this Article

This article does not cover the steps to provisioning a server. This article assumes that your server is ready to install ET. See the System Requirements article for information on the supported operating systems, required applications and the recommended specifications. This article assumes that these requirements have been met.

Before You Begin

  • Back up your ET database and your ET installation directory including all child folders. These will include the web.config file, logging.config file and attachment directory among other files. If you are also exporting your baselines, then we recommend that you also back up this folder.
  • The Server Key will change. The server key depends on the following details;
    1. Machine Name
    2. Processor Count
    3. Operating System Name
    4. Operating System Version (Major and Minor)

More details on Server Keys can be found in this article Server Key Generation.

  • If the URL for your ET instance is also changing you will need to change the site.root.url setting in the web.config file. If you are synchronizing with JIRA and the URL for your ET instance is changing, the URL in JIRA to the ET requirements, scripts, script runs, and incidents will not be update in JIRA until the incident is synchronized again. You may wish to initiate a synchronize all. Before doing so, consider how many entities (issues/ requirements) will be synchronized as this may affect the performance of ET and JIRA during peak usage. You may wish to consider batching entities by using a filter to reduce the number of entities synchronized.
  • If you are moving your production system, we recommend contacting Catch Support in advance to arrange assistance with providing a new license text.

The Migration

  1. After setting up your new ET server, run the ET installer matching the version you are currently running on the ET server you are moving from. You can find the latest version of Enterprise Tester on our website or contact the Support team for older installation files.
  2. Copy across to the new server a copy of the backup copy of your original web.config file to the Enterprise Tester Web folder.
  3. Copy across to the new server a copy of the backup copy of your attachment folder to your Enterprise Tester Data folder or if you have changed the storage of attachments to a non default location (default storage is …\Data\Attachments) then you will need to copy over your attachment directory to the new location on the new ET server and update your web.config file.
  4. Start IIS.
  5. In the browser, navigate to the ET website. A new server key should be displayed. You will need to add a new license text in order to access ET. Email the server key to Catch Support requesting a new license and indicate whether the license is for a production or development environment.
  6. Apply the license text. You should be able to access Enterprise Tester now.

Updating the site.root.url

If the URL for ET is changing, then you will need to update the site.root.url setting in the web.config file. The site.root.url setting configures the URL that will be specified in links back to ET in external systems like JIRA.

To update the site.root.url, open the web.config file. You may need to open this file as Administrator in order to update it.

Locate the section <appSettings> </appSettings>.

There is likely a key value pair for site.root.url already listed. If so, update the value to the new URL. If not, add the following key value pair at the end of the list of app setting before </appSettings>.

This should look like:


<add key=”site.root.url” value=”http://myapp.com/EnterpriseTester/“/>


For more information, please see the article appSettings.

Restart IIS.

If you are synchronizing with an external system you may wish to update your links by initiating a Synchronize All from the project link screen. As noted above, you may wish to consider batching entities for synchronization to reduce the load on ET and your external system if you expect a lot of data to be synchronized.

Updating the Attachment Storage Location

By default, Enterprise Tester stores all attachments in the Data directory of the ET installation files (\Data\Attachments). If you are storing your attachments in a non default location, you will need to update the web.config file to specify the storage location for all attachments.

To do this, you will need to locate or add the attachment.storage.path key to the appsettings in your web.config file.

To update the attachment.storage.path, open the web.config file. You may need to open this file as Administrator in order to update it.

There make be a key value pair for attachment.storage.path already listed. If so, update the value to the new path. If not, add the following key value pair at the end of the list of appSetting before </appSettings>.

This should look like:


<add key=”attachment.storage.path” value=”f:\et-attachments”/>


For more information, please see the article appSettings.

Restart IIS.

Once the web.config file is updated, ET should be able to access all attachments and new attachments will also be saved to this directory.

Upgrades using the bin zip file (Manual installation)

Enterprise Tester, by default, is installed in your C:\Program Files\ or C:\Program Files (x86)\ directory, alongside any other programs you have installed.  The folder can be configured to reside on a different drive if you should choose; throughout this document we refer to this folder using the word %ProgramFiles% to avoid confusion.

Manual Upgrade (Bin Zip Installer)

Manual upgrades require you to be aware of framework upgrades, please refer to the Important Upgrade information at the top of this page.

To upgrade Enterprise Tester manually perform the following steps:

  1. Download the Enterprise Tester installation files from Download Centre
  2. Back Up the following elements of your existing Enterprise Tester installation:
    • Enterprise Tester Database
      • For downloaded trial users this can typically be found in %ProgramFiles%\Catch Limited\Enterprise Tester\Data
    • Enterprise Tester File Structure
      • Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\


If you wish to be a little more selective with the backup, the following files and folders should be included

  • Logging.config & Web.config Files
    Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\Web
  •  Attachments
    Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\Data\Attachments\
  • Avatars
    Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\Data\Avatars\
  • Optional: Indexes
    Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\Data\Indexes\
    If you do not back this up and need to roll back the upgrade you will need to perform a full reindex of the ET instance


3. Extract the files from the downloaded bin.zip file and copy all of the contents from the “\Web\ folder EXCLUDING
the following:

    • \App_Data\ folder
    • Web.config file
    • Logging.config file

4. Navigate to %ProgramFiles%\Catch Limited\Enterprise Tester\Web folder and delete the existing folders of the same
names as those copied above

5. Paste in the content copied in Step 3, choose to overwrite any files when prompted.

6. Using the command line navigate to the %ProgramFiles%\Catch Limited\Enterprise Tester\Web\Bin\ folder and run
“Postinstalltasks.exe ziprelease”.  Administrator permissions may be required.

7. Make sure the identity that runs Enterprise Tester (as seen in the IIS application pool configured during installation)
still has write permissions to the “\data” and “\web\app_data\” directories.

8. Restart IIS

9. Start Enterprise Tester. Enterprise Tester may take a few minutes to start up as any necessary database schema changes are made.

If Enterprise Tester does not start you may need to remove the System.Data.SQLite.dll in the Web\Bin folder.

Upgrades using the installer file

Enterprise Tester, by default, is installed in your C:\Program Files\ or C:\Program Files (x86)\ directory, alongside any other programs you have installed.  The folder can be configured to reside on a different drive if you should choose; throughout this document we refer to this folder using the word %ProgramFiles% to avoid confusion.

Installer File Upgrade

To upgrade Enterprise Tester using the installer, perform the following steps:

  1. Download the Enterprise Tester installation files from the latest version page.
  2. Stop IIS
  3. Back Up the following:
    • Enterprise Tester Database
      • For downloaded trial users this can typically be found in %ProgramFiles%\Catch Limited\Enterprise Tester\Data
    • Enterprise Tester File Structure
      • Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\

If you don’t want to back up the entire file structure, these are the specific files needed for restoration:

    • Logging.config & Web.config Files
      • Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\Web
    • Search Index folder
      • Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\Web\app_data\Index
    • Attachments stored in your File System
      • Typically located in %ProgramFiles%\Catch Limited\Enterprise Tester\Data\Attachments\

     4. Check IIS Settings so you can reset them if they are changed by the installer.

5. From the downloaded installer, run the .exe file.  This will elevate permission to “Run as Administrator” to ensure all
upgrade files can be installed.

6. Restart IIS

7. Start Enterprise Tester.  Enterprise Tester may take a couple of minutes to start up, it will be applying database
schema migrations to update the database structure.

If you have changed IIS settings you may need to reapply defaults to upgrade via the installer and then reapply the settings after the upgrading:

IP Address: All unassigned
Port 80
No host header configured
Virtual directory named “EnterpriseTester”

Upgrades & Compatibility

Important Upgrade Information

1) Always upgrade your DEV/TEST Environment before PROD to verify your upgrade process.

2) If you are using Enterprise Tester 5.0 or below, you must first upgrade to Enterprise Tester version 5.1 , then upgrade to Enterprise Tester version 6.0.

  • Once you have successfully upgraded to Enterprise Tester version 6.0 you can then upgrade to the latest version of Enterprise Tester. 

3) Enterprise Tester 6.1 and above requires  .Net Framework 

4) Always check external system compatibility below before upgrades.


 Upgrade Types


External System Compatibility

Before upgrading please verify compatibility with external systems.

Catch Software Product

Compatible Version


Compatible Version

Enterprise Tester5.x to 6.0JIRA6.x
Enterprise Tester6.1 +JIRA7.0 – 7.8
Enterprise Tester6.1 +Confluence5.8, 5.9
Enterprise Tester6.1 +Enterprise Architect11, 12


Custom results using XSLT data (custom XML to J-Unit)
Microsoft MS Test
Parasoft C+++test
DuetteAllRational Functional Tester8.1, 8.2
DuetteAllQuick Test Pro10, 11
DuetteAllSelenium HTML SuiteHTML Suite
Rover1.1See Enterprise Tester Integration
Compiler Suite1.0See Enterprise Tester Integration

Initial Login and Licensing

Before you can use the application you will need to configure your organization name, an administrative user and license details. You will be prompted to do this the first time that you launch the application.

You will need to use this Username/Password to log onto the system.

Generating a License Key

To do this copy the server key as listed on the screen and send it to Catch Sales to assist you in generating a license.  The sales team will provide you with the licence text required to enable your license.

Enter the license text into the Enterprise Tester License Text field and click on ‘Save’.

You are now ready to logon to Enterprise Tester.

SQL Login

Configuring SQL Server and Enterprise Tester to Use a SQL Login

This guide walks through the steps for creating a SQL login and updating the web.config file for Enterprise Tester using the login for authentication.

Create a SQL user name/login on the server you wish to access

  • Open SQL Server Management Studio.
  • Connect to the SQL server.
  • Go to security->logins.
  • Right click, select “New Login”.

  • Select SQL Login.
  • Enter the username and password you wish to use.
  • Disable password policy enforcement, and ensure that the login does not expire, and does not require changing on next login.

  • Click on user mappings.
  • Find the Enterprise Tester database.
  • Click the checkbox next to it, to give the new user access.
  • Ensure the new user has either public and db_owner permissions, or public, datareader, datawriter and ddl permissions (as shown in the following screen shot).

  • Click “OK” to save this new user.

Update the web.config file, so it uses the new SQL server login/password

  • Locate Enterprise Tester’s web.config file (normally in C:\Program Files\Catch
  • Limited\Enterprise Tester\Web\web.config).
  • Open the file with a text editor.
  • Locate the <connectionStrings> section in the configuration file.
  • Update the connection string, removing any of the following properties:

    o Integrated Security=True;

    o AttachDbFilename=<path>;

    o Trusted_Connection=Yes;

  • Add the User Id and Password properties, for the login/password you created prior.
  • Save changes to the web.config file.
  • Access the Enterprise Tester website, to ensure the database changes have worked.

User attached instance migration

User Attached Instance Migration after Data Recovery

This guide is intended to provide directions on how to migrate away from a User Attached instance to a standard database instance after data recovery has been performed. For details on what a user instance, see this MSDN article: http://msdn.microsoft.com/en-us/library/ms254504.aspx


To proceed with migrating away from a user instance you will need to:

Last of all, before commencing installation please reboot the machine, and stop the IIS service (Start -> Control Panel -> Administrative Tools -> Internet Information Services -> local computer (right click) -> Restart IIS -> Stop Internet Services). This should prevent users from accessing Enterprise Tester, causing the existing database to attempt attachment.

Restoring the Database

Launch the Sql Server Management Studio via:

Start -> Microsoft Sql Server 2005 -> SQL Server Management Studio Express

Once loaded, connect to your local SQL Express instance (this should just be matter of clicking the connect button). If the Server Name textbox is blank then enter the text “.\SqlExpress” before clicking the “Connect” button.

Once connected expand the right hand tree node, then right click on the “Databases” node and select “New Database…”.

Enter “EnterpriseTester” as the database name, and click OK.

Expand the “Databases” node, you will now see a child database node underneath “EnterpriseTester”.

Right click on the “EnterpriseTester” node, select Tasks -> Restore -> Database.

On the Restore Database dialog, select the “From device” radio button.

Click the Elipsis button “…” to the right of the “From Device:” radio button.

Click the “Add” button.

Browse to the location where you saved the database backup file ending with the extension .bak, and select it.

Click “OK”.

Click the Restore “checkbox” next to the first entry in the “Select the backup sets to restore” list.

Click the “options” link on the left hand side, to view the options page.

Click the checkbox next to “Overwrite the existing database”.

You will see two entries “EnterpriseTester” and “EnterpriseTester_log” with the following “Restore  As” paths.

Double click on “Restore As” and change the paths from:



C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\EnterpriseTester.mdf
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\EnterpriseTester_log.LDF

Alternatively you can browse for these paths by clicking the Elipsis “…” button next to each path.

Click the “OK” button to proceed with restoring the backup.

Once completed you should see the message “The restore of database ‘EnterpriseTester’ completed successfully’.

Changing the Enterprise Tester Connection String

Open windows explorer.

Navigate to the Enterprise Tester installation directory (normally c:\Program Files\Catch Limited\Enterprise Tester)

Navigate to the subdirectory “Web”.

Open the file called “web.config” with a text editor, such as windows notepad.

Locate the default connection string, which should look similar to this:

<add name="Default" connectionString="Data
Source=.\SQLExpress;AttachDbFilename=C:\Program Files (x86)\Catch Limited\Test
Management System\Data\EnterpriseTester.mdf;Initial
Catalog=EnterpriseTester;Trusted_Connection=Yes;" />

And then replace the connection string with the following:

<add name="Default" connectionString="Data Source=.\SQLExpress;Initial
Catalog=EnterpriseTester;MultipleActiveResultSets=true;Trusted_Connection=Yes;" />

Test It

Restart the IIS service (Start -> Control Panel -> Administrative Tools -> Internet Information Services -> local computer (right click) -> Restart IIS).

Access the Enterprise Tester website, you should be presented with a login screen.

If instead an error is displayed the contact customer support and supply them with the following

  • The log.txt file (found c:\Program Files\Catch Limited\Enterprise Tester\Web\App_data).
  • A screen shot or copy of the error message displayed when accessing the website.
  • Version of Enterprise Tester.
  • Operating System, Version & Service Pack details.

Performing Backups

Now that you have migrated away from a user instance, you should no longer user file copy to backup your database. Instead backups should be performed via Sql Management Studio.

This guide on MSDN provides details on how to do so:


Backups of databases can be automated as well with some simple scripting, more details can be
found here:


Backup Support

Please note that backing up databases, and automation of backups is outside the scope of the support Catch Limited provides to Enterprise Tester customers – additional support needs to be handled by your in-house database administrators and database vendors.

Data migration from Trial version of Enterprise Tester


This guide provides information on how to backup data from Enterprise Tester, and how to migrate from the trial version database to another version of sql server.

Backing up data from your trial version of Enterprise Tester.

Enterprise Tester, when installed via the MSI file, will use Sql Server Express Edition 2005 to store it’s data, making use of a feature of sql server express, which allows attaching a database file upon connect. While trialing and evaluating Enterprise Tester this provides a simple set-up, which makes it easy to uninstall the product cleanly at a later date, or to apply updates.

To backup your data while in this set up, the easiest approach is to stop the sql server express database server, copy the data files, and restart it again.

Stopping Sql Server Express

You can stop the Sql Server Express Edition server, by loading the services snap-in:Start -> Control Panel -> Administative Tools -> Services

Once loaded, locate the sql server express service, which normally has the name:SQL Server (SQLEXPRESS)

Right click, and select “Stop”. This will stop the service, which will allow the database files to be copied.

Copying the data files

Open windows explorer, and browse to the data folder of your Enterprise Tester install folder i.e. c:\Program Files\Catch Limited\Enterprise Tester\Data\

In this directory will be two files:

  • EnterpriseTester.mdf
  • EnterpriseTester_log.LDF

Copy these two files to another location, these are the backup files which you can restore at a later date if something goes wrong.

Restarting the Sql Server Express database server

Once your have completed the backup, right click on the “SQL Server (SQLEXPRESS)” service, and select “Start” to restart sql server express edition, at which point you can start using Enterprise Tester again.

Migrating your trial database to a be a permanent sql server Database


When putting Enterprise Tester into production use, it’s recommended that you stop using the default “attach on connect” approach employed by the msi installer, and instead instantiate a permanent Sql Server or Sql Server Express database.

Advantages of permanent database

The advantages of doing this include:

  • Your database administrator can handle configuring scheduled daily backups and maintenance.
  • You can query the database using reporting tools.
  • You can easily backup and restore snapshots of the database to create test / training versions of ET.

Before you start

Before starting the migration – you must have the sql server management studio tool available.If you do not, it can be downloaded and installed from microsoft:


These instructions assume the tools are installed on the same machine as Enterprise Tester.

Step 1 – Restart or Stop IIS

Either through IIS Manager:

  • Click on Start -> Control Panel -> Administrative Tools -> Internet Information Services(IIS) Manager
  • Right click on local machine node (should have the same name as your computer) and select Stop, or in IIS6, select All Tasks -> Restart IIS.

Alternatively you can open a windows command prompt and type “iisreset” – this will stop and restart IIS on the local machine, if you have the IIS command line tools installed.

Step 2 – Attach the database files in Sql Server Express.

Sql Server not Supported

These files cannot be directly attached in the Standard or Enterprise editions of Sql Server, the data files use compression which is incompatible with the non-express editions of Sql Server – so you must first attach them in the Express Edition of Sql Server, then create a backup of the databases, which can be restored into any version of Sql Server.

Start Sql Server Management Studio or Sql Server Express Management Studio.

When prompted to connect, connect to the .\sqlexpress database.

Once connected, right click on the “Databases” folder and select “Attach”.

The attach database dialog will appear. Click the “Add” button to attach the database file, browse to the Install folder of Enterprise Tester, and select the Data\EnterpriseTester.mdf. Normally the database is located in “C:\Program Files\Catch Limited\EnterpriseTester”.

Once the file is selected, the attach database dialog will look like this:

It’s suggested you change the name given to the attached database, so that it’s “EnterpriseTesterTrial”, like so:

Click OK to attach the database, it should now appear in the list of databases.

Backing Up the Database

Now that the database is attached, we can back it up – this will then allow us to restore the database onto any sql server we like. Right click on the EnterpriseTesterTrial database, then select Tasks -> Backup…

This will display the backup dialog, select a location for your backup file i.e. c:\temp\EnterpriseTesterTrial.bak and then click ok.

You will now have a backup of the Enterprise Tester trial database.

Restoring the database on another server

You can now restore the database on another server, such as the sql server your environment already uses for other applications. To do so you must:

  • First, create a new database, that will be the target for the restoration.
  • Restore the database.

To create a new database, right click on the “Databases” and select “New Database…”.The new database dialog will display:

Enter a name for your database, such as “EnterpriseTester” and click OK. A new database will appear in the tree with the name “EnterpriseTester”. Right click on this node, and select Tasks -> Restore Database…, the restore database dialog will appear.

From here you must select the location of the backup you wish to restore, locate the file from the previous step i.e. c:\temp\EnterpriseTesterTrial.bak.

Once a backup file has been selected, you must then select which backup to restore – there should be only a single item, just click the checkbox next to it.

Once the backup has been selected, select the “Options” page.

  • Check “Overwrite the existing database (WITH REPLACE)”.
  • Edit the “Restore As” value for both the “EnterpriseTester” and “EnterpriseTester_log” database files.
  • By default these will be pointing the old location of the database files from the attached database, you must browse and locate the existing database and log files that you created when adding the database.
  • Click OK to restore the database.

Finding the existing location of database files

The location of database files can vary greatly, you can determine the correct location by:

  • Right clicking on the “EnterpriseTester” database and selecting Properties.
  • When the properties dialog displays, select the “Files” page.
  • Under “Database Files” scroll the display to the right, until you can see the “Path” column. This will display the path for each database files, use these paths when restoring the database from the trial version backup.

Changing the connection string for the application

Now that the database has been moved you must change the connection string for the application.

In the installation directory of Enterprise Tester, locate the “web.config” file, which is stored in the “Web” subdirectory.

Open this file with a text editor, and locate the “<connectionStrings>” section, which should look like this:

<add name=”Default” connectionString=”Data Source=.\SQLExpress;AttachDbFilename=C:
\Program Files\Catch Limited\Enterprise Tester\Data\EnterpriseTester.mdf;Initial

You must now replace the existing connection string,
i.e. Data Source=.\SQLExpress;AttachDbFilename=C:\Program Files\Catch Limited\Enterprise
Tester\Data\EnterpriseTester.mdf;Initial Catalog=EnterpriseTester;User
with the connection string for the new sql server database.

If, for example our server was called “SQLPROD1″, this might mean we change the connection string to be:

<add name=”Default” connectionString=”Data Source=SQLPROD1;Initial

For examples of valid Sql Server connection strings, please see the following website:

Once you have made your changes, click save, and then refresh Enterprise Tester in the browser to make sure it worked correctly.

Required Database Permissions

The user that accesses the database must have permissions to add, remove and alter tables and foreign keys. This is required by the automatic migration support in Enterprise Tester, which handles upgrading the database schema automatically.

Because this access is only required during upgrades, it is possible for a Database Administrator to enable it during an upgrade, and once Enterprise Tester has successfully started, to remove the permissions from the user (or to change which user accesses the database).

Database configuration

To change which database is being targeted, the web.config file must be edited, and at a minimum there are 3 options which must be changed to support each database engine – as per the table below:

Oracle is no longer a supported database for Enterprise Tester.

Database ProductMigrator ProviderNHibernate DriverNHibernate Dialect
MySQLMigrator.Providers.Mysql.MysqlDialectNHibernate.Driver.MySqlDataDriverEnterpriseTester.Core.Dialects.MySqlDialectEx, EnterpriseTester.Core
SQLServer 2012 (and above)Migrator.Providers.SqlServer.SqlServer2005DialectNHibernate.Driver.SqlClientDriverNHibernate.Dialect.MsSql2005Dialect

Database Specific Notes on Setting the Character Set


Enterprise Tester supports unicode strings in MySql databases, but you must ensure some steps are followed during initial setup.

Step 1 – Database Creation

When creating the database, you must specify UTF8 as the default character set and utf8 case insensitive as the default collation: 

 CREATE DATABASE `enterprisetester` CHARACTER SET utf8 COLLATE utf8_general_ci; 

Step 2 – Configuring Character Set in Connection String

If your connection string to the MySql database is: 

<add name="Default" connectionString="Server=;Database=enterprisetester;Uid=etuser;Pwd=etpass" />

Then you must append the UTF8 character set declaration to end, like so:

<add name="Default" connectionString="Server=;Database=enterprisetester;Uid=etuser;Pwd=etpass;CharSet=utf8;" />

If you have not set the UTF8 character set, there are ways to change the character set through a process of dumping out the database, performing a search/replace of all character set / collation declarations, then importing the modified database dump. Please consult your in-house MySql DBA for assistance.


Enterprise Tester supports unicode strings in Postgresql databases, but you must ensure some steps are followed during initial setup of the database. Before beginning, make sure you have a version of PostgreSQL that supports a column type of “uuid” (normally version 8.3 and later) as this is required by Enterprise Tester.

PostgreSql Databases must be created with a unicode encoding and we recommend using “UTF-8”. If you use a non-unicode encoding such as WIN1252 Enterprise Tester will still work, but you may experience some issues when restoring baselines from other ET instances, importing data or when users save textual data that contains unicode characters.

For Postgresql to support unicode strings, you must create the database with the ‘UTF8’ encoding, like so: 

CREATE DATABASE "enterprisetester"
  WITH OWNER "postgres"
  LC_COLLATE = 'en_US.UTF-8'
  LC_CTYPE = 'en_US.UTF-8';

Unlike MySql there is no need to change the connection string to accommodate UTF8 encoding. If you wish to learn more about setting the locale and collation for a PostgreSql database, please refer to the PostgreSql documentation: 


Example Connection Strings

Each database also uses a slightly different connection string format – the http://connectionstrings.com/ website provides useful details of each connection string format.

Database ProductExample Connection String
SQL Server Express (user-attached database)DataSource=.\SQLExpress;AttachDbFilename=C:\ProgramFiles(x86)\CatchLimited\EnterpriseTests\Data\EnterpriseTester.mdf;InitialCatalog=EnterpriseTester;Trusted_Connection=Yes;
SQL Server (Integrated Security)DataSource=.\SQLExpress;Initial Catalog=EnterpriseTester;IntegratedSecurity=True;
SQL Server (SQL username/password)DataSource=dbserver;Initial Catalog=EnterpriseTester;UserId=etuser;Password=etpass;

Configuring a PostgreSQL Database

Before beginning, make sure you have a version of PostgreSQL that supports a column type of “uuid” (normally version 8.3 and later) as this is required by Enterprise Tester.

Configure web.config to connect to a database


Within the web folder you will find the file “web.config” – this is a XML file containing a number of settings which configure settings for the Enterprise Tester application, including what type of database to connect to and its connection string details.

By default this file is located:

c:\Program Files\Catch Limited\Enterprise Tester\Web\web.config

Open the file using notepad, within it you will need to change 4 settings:

  • “migration.providerName”
  • Default connection string
  • connection.driver_class
  • dialect

These are the default settings:


          <add key="migration.providerName" value="Migrator.Providers.SqlServer.SqlServer2005Dialect" />  

Default connection string

<add name="Default" connectionString="Data Source=.;Initial Catalog=EnterpriseTester;Integrated Security=True;MultipleActiveResultSets=true;" />


<add key="connection.driver_class" value="NHibernate.Driver.SqlClientDriver" />


<add key="dialect" value="NHibernate.Dialect.MsSql2005Dialect" />

Following are the web.config values you will need for each type of database:

We provide example connection strings for each database, but each database supports a number of different connection options – we recommend consulting the http://connectionstrings.com/ website for listings of the different connection strings you can try.

SQL Server

By default the web.config file comes with the settings necessary to connect to Sql Server or Sql Server Express – all you need to do is provide a connection string.

Your options are:

  1. Use the provided database with user-attached connection string.
<add name="Default" connectionString="Data Source=.\SQLExpress;AttachDbFilename=c:\inetpub\wwwroot\EnterpriseTester\Data\EnterpriseTester.mdf;Initial Catalog=EnterpriseTester;Trusted_Connection=Yes;"/>

2. Connect to an existing database, using integrated security.

When using integrated security, the database will be connected to using the username configured as the identify for the application pool in IIS.

<add name="Default" connectionString="Data Source=.\SQLExpress;Initial Catalog=EnterpriseTester;Integrated Security=True;" />

3. Connect to an existing database, using a sql username & password.

<add name="Default" connectionString="Server=Server123;Database=EnterpriseTester;User ID=bob;Password=pass123;Trusted_Connection=False;" />


Change Enterprise Tester to use these values:

migration.providerName: “Migrator.Providers.PostgreSQL.PostgreSQL82Dialect”
connection.driver_class: “NHibernate.Driver.NpgsqlDriver”
dialect: “NHibernate.Dialect.PostgreSQL82Dialect”

And update the connection string to be like this:

<add name="Default" connectionString="Server=;Port=5432;Database=et-prod;User Id=postgres;Password=Password123;Timeout=60;CommandTimeout=120;" />


Change Enterprise Tester to use these values:

migration.providerName: “Migrator.Providers.Mysql.MysqlDialect”
connection.driver_class: “NHibernate.Driver.MySqlDataDriver”
dialect: “EnterpriseTester.Core.Dialects.MySqlDialectEx, EnterpriseTester.Core”

And update the connection string to be like this:

<add name="Default" connectionString="Server=;Database=et-prod;Uid=etuser;Pwd=password;" />

More examples of connection strings can be found here: http://connectionstrings.com/mysql#p28