Re: Locks and ADO
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Sat, 18 Nov 2006 14:52:32 -0500
Ralph wrote:
"Christian Schaeffler" <newsfeed@xxxxxxxxxxxxxx> wrote in message
news:eUewdniCHHA.5012@xxxxxxxxxxxxxxxxxxxxxxx
Hello newsgroup!
Please let me quote a post I made to the SQL Server newsgroup. In
fact the ADO question fits better in here I think.
[quote]
We are using SQL Server as database for an application. Recently we
faced some deadlock errors and now I'm trying to understand what
happens...
I already did the basic tracing with SQL Profiler and the DBCC
TRACEON (3605,1205,-1) parameters and isolated some deadlocks with
this method.
So my questions are more to the basics to learn how avoid those
problems. [...]
3. Since most of the queries we use are launched out of the source
code of our application, what would be the better (= safer) method?
Using the ADODB.Connection.Execute statement or openening a ADO
recordset and using ADO's integrated methods?
[/quote]
Any hints are welcome.
I'm not sure I completely understand your question, but perhaps it
will be useful to note that NO database (or RDBMS) can guarantee
"concurrency".
Maybe I muddied the waters by talking about concurrency, which had nothing
to do with the OP.
Deadlocks have more to do with the order in which statements are executed
than concurrency. So I will agree with you that how the execution is
performed is irrelevant.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
.
- Follow-Ups:
- Re: Locks and ADO
- From: Ralph
- Re: Locks and ADO
- References:
- Locks and ADO
- From: Christian Schaeffler
- Re: Locks and ADO
- From: Ralph
- Locks and ADO
- Prev by Date: Re: Locks and ADO
- Next by Date: Re: Locks and ADO
- Previous by thread: Re: Locks and ADO
- Next by thread: Re: Locks and ADO
- Index(es):
Relevant Pages
|
|