SQL Server How to Prevent Locking To Do Read-Only Reports

[Abe]

Need some information regarding SQL Server locking.

Requirement is to run SQL Statements for reports (read-only) that will
not lock-out other people trying to update (write lock). For this, we
tried the following to make the db connection not deny write locks
(our report code will not have a read-only lock).

ADODB.Connectio nObj.Mode =adModeShareDen yNone

But this made our connection bumped whenever someone tried to update.

Tried enabling dirty reads by doing:

ADODB.Connectio nObj.IsolationL evel =adXactBrowse

Even this made our connection bumped whenever someone tried to update.

Is there a way to achieve what is needed without having a seperate
database for reports?

[Steve Jorgensen]

Re: SQL Server How to Prevent Locking To Do Read-Only Reports

It sounds like you need a separate database for OLAP.

On 12 Feb 2004 13:11:04 -0800, AbeShakered@hot mail.com (Abe) wrote:
[color=blue]
>Need some information regarding SQL Server locking.
>
>Requirement is to run SQL Statements for reports (read-only) that will
>not lock-out other people trying to update (write lock). For this, we
>tried the following to make the db connection not deny write locks
>(our report code will not have a read-only lock).
>
>ADODB.Connecti onObj.Mode =adModeShareDen yNone
>
>But this made our connection bumped whenever someone tried to update.
>
>Tried enabling dirty reads by doing:
>
>ADODB.Connecti onObj.Isolation Level =adXactBrowse
>
>Even this made our connection bumped whenever someone tried to update.
>
>Is there a way to achieve what is needed without having a seperate
>database for reports?[/color]