Quote:> What is the fastest transaction isolation level and how can I make sure my
> DB is using it? I have a database that is used by an application which is
> primarily transaction driven. The odds of two people trying to change the
> same record at the same time are slim to none, and even if they do I'm
> willing to deal with lost data.
This is probably posted in the wrong group and is a simple question, but:
For report purposes I'd like to have the isolation level set to
READ UNCOMMITTED or "dirty reads" or "no lock". In our application that
would be acceptable. I can't count on our users to set this when
Is there any way to configure SQL server for this default?
Is there a way to run a stored procedure upon login where I can
place the SQL command to set the isolation level?
Thanks for any help