Re: Concurrency problem
- From: "Cor Ligthert[MVP]" <Notmyfirstname@xxxxxxxxx>
- Date: Fri, 20 Feb 2009 09:15:59 +0100
Johnny,
I did not make much attention that you was using a transaction.
A transaction is in my idea something that should be avoided as much as possible, because it can lock your tables unwished completely
In this case therefore in my idea completely stupid.
Cor
"Jonny Bergdahl" <jonny.bergdahl@xxxxxxxxxxxxxxxx> wrote in message news:EEB8F159-0AB2-42E9-ABA8-D7D1E54DC1C6@xxxxxxxxxxxxxxxx
I have a GUI application that displays historical data, and a batch application that loads new data into the database.
My problem is that while the baych application is updating the database, the GUI application gets locked out. The batch application is using one transaction for the update, which can run for up to 15 minutes.
Question is what properties do I need to set on the Connection/Command objects to let the GUI ignore the locks and access the data anyway? Since it it historic data it is not important that it is not fully up to date, what is important is that the user is not locked out during the update.
I am using SQL Server 2005, ADO.NET with a MSDTC transaction, and C#.
Any help is much appreciated!
regards;
/jb
.
- References:
- Concurrency problem
- From: Jonny Bergdahl
- Concurrency problem
- Prev by Date: RE: full documentation for odbcconnection.getschema?
- Next by Date: Re: Retrieving Rows Affected Counts
- Previous by thread: Re: Concurrency problem
- Next by thread: RE: full spec of standard selects using INFORMATION_SCHEMA?
- Index(es):
Relevant Pages
|
