Locks and ADO
- From: "Christian Schaeffler" <newsfeed@xxxxxxxxxxxxxx>
- Date: Fri, 17 Nov 2006 10:22:10 +0100
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.
--
Thanks in advance for your help
Christian
--- my bad English is not my worst problem ---
.
- Follow-Ups:
- Re: Locks and ADO
- From: Ralph
- Re: Locks and ADO
- From: Bob Barrows [MVP]
- Re: Locks and ADO
- Prev by Date: CursorLocation for Execute Method
- Next by Date: Re: CursorLocation for Execute Method
- Previous by thread: CursorLocation for Execute Method
- Next by thread: Re: Locks and ADO
- Index(es):
Relevant Pages
|