Summary

MSDE contains a concurrency workload governor that limits the performance of the SQL server database engine whenever the engine receives more than five Transact-SQL batches. As more batches are submitted, the concurrency governor continues to slow down the system. The additional batches are not dropped or lost, merely processed with degraded performance. When activated, the concurrency governor affects all connections; it is not limited to degrading performance for only the connections that activated the governor.

A Transact-SQL batch is a group of one or more Transact-SQL statements sent from LaserFiche to SQL Server. LaserFiche communicates with SQL Server through Transact-SQL statements. All actions that involve viewing or modifying data stored in a SQL Server database are performed through Transact-SQL statements.

More Information

You can use the DBCC CONCURRENCYVIOLATION statement to report how often the concurrency governor is activated.

1. Click Start and then click Run.
2. Open a command prompt by typing in the following in the Run dialog box:

   cmd

3. Click OK.
4. In the command prompt window, type the following line to start the OSQL utility:

   osql -E -S ComputerName\LaserFiche

5. Type the following to check how often the concurrency governor is activated.

   DBCC CONCURRENCYVIOLATION
   GO

6. If the concurrency governor has ever been activated, the output will display the number of activation times.

Note: If you experience significant performance degradation and testing reveals that the workload governor is frequently activated, you should consider upgrading to a full version of Microsoft SQL Server.