Home > Alerts > Installation > SQL Server Configuration

SQL Server Configuration

In order to connect to the required version of SQL Server, it may be necessary to adjust the settings in the alertEngine.properties file or the TCP/IP port settings for the SQL Server instance.

The following link is to an MSDN forum which tells you how to change the TCP/IP port settings for SQL Server 2005.  

http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/d91d265a-59d3-4c8a-94ad-227611c342d8/

The default port setting in the properties file is 1433 – for example:

jdbc:sqlserver://127.0.0.1:1433;databaseName=Alerts

which is the default for the TCP/IP port in SQL Server 2005.

Named Instance

If you have multiple instances of SQL Server installed on your machine and want to use something other than the default instance for your Alerts Engine installation you can specify the instance in the JDBC property. The example below sets the URL for the Alerts database to connect to the SQLEXPRESS2005 named instance (on port 2409).

alerts.jdbc.url=jdbc:sqlserver://127.0.0.1:2409;instanceName=SQLEXPRESS2005;databaseName=ALERTS

SQL Server 2008

If you are using SQL Server 2008 you will need to replace the version of the SQLJDBC.JAR used by the Alerts Engine. The WAR file (versions 1.1 and higher) includes the default SQLJDBC.JAR and the SQL Server 2008 implementation SQLJDBC4.JAR. Both of these files will be unzipped into the folder ~\AlertEngine\WEB-INF\lib.

For a SQL Server 2008 installation, rename SQLJDBC.JAR to SQLJDBC.JAR.2005 and copy SQLJDBC4.JAR to SQLJDBC.JAR. Restart Tomcat.

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)