|
|
Posted by Robert on 03/02/06 01:36
Thanx Erland, unfortunately read-only is not a viable option. We have be
reviewing the database and are putting in indexes and hints on the queries
to determine if the locking will become less of a problem. The users are
engaged in some practices that have been going on for awhile and there
application keeps timing out when a lock is placed on a table for more that
30 seconds. The biggest problem we have seen are the locks created by the
ad hoc queries from Access and Excel. Until we can convince the dbo to
setup an olap database or stop using Access I think the problems will
continue.
"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns9779F28923052Yazorman@127.0.0.1...
> Robert (robert.j.sipe@boeing.com) writes:
>> Rather than setting by session I would like to configure the DB as read
>> uncommitted.
>
> You can set the database read-only to eliminate locking entirely.
>
> But else you can't do it, and that is probably a good thing. Dirty reads
> is nothing you should engage in as a matter of routine. Maybe you should
> review indexing in your database instead.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|