To connect CrowdID to MS SQL Server,
1. Configure SQL Server
- Create a database user which CrowdID will connect as (e.g. crowduser).

In SQL Server, the database user (crowduser above) should not be the database owner, but should be in the
db_owner role. - Create a database for CrowdID to store data in (e.g. crowdiddb).
This must be a different database to the one used by Crowd. - Ensure that the user has permission to connect to the database, and create and populate tables
2. Copy the SQL Server driver to your application server
- Download the SQL Server JDBC driver from JTDS (recommended, assumed below), or I-net software (commercial).
- Add the SQL Server JDBC driver jar (jtds-[version].jar) to the
common/libdirectory.
3. Configure your application server to connect to SQL Server
- Edit the conf/Catalina/localhost/crowd.xml and customise the username, password, driverClassName and url parameters for the Datasource.
- Delete the minEvictableIdleTimeMillis, timeBetweenEvictionRunsMillis and maxActive attributes (which are only needed for HSQL, and degrade performance otherwise).
4. Configure CrowdID to use MS SQL Server
- Edit the build.properties file (located in the root of the Standalone distribution) and modify the hibernate.dialect to the following:
hibernate.dialect=org.hibernate.dialect.SQLServerDialect
- Then run the ./build.sh or build.bat. This will configure CrowdID to use the MS SQL Server dialect.
There is a problem with build.batin Crowd version 1.2.0. To fix the problem, please apply the patch described in CWD-638.
If you do not wish to edit this file and run the build script, you can edit the jdbc.properties (which the above script modifies) directly. The jdbc.properties file is located here: crowd-openidserver-webapp\WEB-INF\classes\jdbc.properties; modify the file to the following:
# - Crowd Configuration Options hibernate.connection.datasource=java\:comp/env/jdbc/CrowdIDDS hibernate.dialect=org.hibernate.dialect.SQLServerDialect hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory ...
Next Steps
You should now have an application server configured to connect to a database, and CrowdID configured to use the correct database. Now start up CrowdID and watch the logs for any errors.






