416.467.9100 | Dundas Data Visualization | Login
Welcome Guest
Dashboard v5.0

This site makes extensive use of JavaScript.

Please enable JavaScript in your web browser and reload the page before proceeding.

Deadlock and Timeout Issues

Hide navigation
RSS
Modified on Mon, 17 Dec 2012 01:39 PM Categorized as Level-Advanced, Troubleshooting

Known Issue

When multiple users are working with Dundas Dashboard concurrently, they may experience intermittent deadlock or timeout errors.

This problem may happen with Dundas Dashboard version 2.5.x or earlier.

Resolution

Use Snapshot Isolation

To resolve this problem, modifications must be made to the Dundas Dashboard DataStore and Sync databases. Specifically, the default isolation level in each of these two databases must be changed to snapshot isolation level.

The following procedure should be performed by a database administrator, for each of the two databases in turn:

Step 1: Enable ALLOW_SNAPSHOT_ISOLATION

Execute the following command on your database:

ALTER DATABASE [YourDatabase]
SET ALLOW_SNAPSHOT_ISOLATION ON

Step 2: Enable READ_COMMITTED_SNAPSHOT

In order to set the READ_COMMITTED_SNAPSHOT flag on your database, all connections (other than your own) to the database must first be terminated as follows:

  1. Run the SP_WHO2 system stored procedure against the database.
  2. Use the KILL system stored procedure to terminate each connection to the database by id. You should be able to kill all but one connection (your own).

Next, execute the following command on your database:

ALTER DATABASE [YourDatabase]
SET READ_COMMITTED_SNAPSHOT ON

Confirming the result

You can confirm applying READ_COMMITTED_SNAPSHOT for the Dundas Dashboard databases after you apply it using this query:

SELECT is_read_committed_snapshot_on FROM sys.databases WHERE name= 'database name'

Related topics

About Dundas | Contact Us Follow us on Twitter! | Privacy Statement | Report Site Issues

Copyright © 2009-2014 Dundas Data Visualization, Inc.