deadlocks not resolved by SQL Server

I am under the impression that SQL Server would automatically detect a
deadlock and roll back a participating transaction. However, I have had a
few cases where automatic resolution did not occur. Instead, I had to go in
and manually kill the transaction that is causing a deadlock.
Is there anyway to avoid this? I don't want to have to manually kill a
transaction to unwind a deadlock if that's at all possible.
Thanks in advanceHi
It sounds like you have prolonged blocking rather than a deadlock, in which
case your query should timeout. Make sure that your application has
overridden the default timeouts and requested to wait indefinitely.
You should also investigate if you application has long running transactions
that have not been correctly committed/rolled back or if poor indexing is
affecting performance.
John
"C.W." wrote:
> I am under the impression that SQL Server would automatically detect a
> deadlock and roll back a participating transaction. However, I have had a
> few cases where automatic resolution did not occur. Instead, I had to go in
> and manually kill the transaction that is causing a deadlock.
> Is there anyway to avoid this? I don't want to have to manually kill a
> transaction to unwind a deadlock if that's at all possible.
> Thanks in advance
>
>

deadlocks not resolved by SQL Server

I am under the impression that SQL Server would automatically detect a
deadlock and roll back a participating transaction. However, I have had a
few cases where automatic resolution did not occur. Instead, I had to go in
and manually kill the transaction that is causing a deadlock.
Is there anyway to avoid this? I don't want to have to manually kill a
transaction to unwind a deadlock if that's at all possible.
Thanks in advanceHi
It sounds like you have prolonged blocking rather than a deadlock, in which
case your query should timeout. Make sure that your application has
overridden the default timeouts and requested to wait indefinitely.
You should also investigate if you application has long running transactions
that have not been correctly committed/rolled back or if poor indexing is
affecting performance.
John
"C.W." wrote:

> I am under the impression that SQL Server would automatically detect a
> deadlock and roll back a participating transaction. However, I have had a
> few cases where automatic resolution did not occur. Instead, I had to go i
n
> and manually kill the transaction that is causing a deadlock.
> Is there anyway to avoid this? I don't want to have to manually kill a
> transaction to unwind a deadlock if that's at all possible.
> Thanks in advance
>
>

dbo can't bring DB online

I have a user with db_owner status who can take a DB offline, but for some r
eason can't bring it back online. The DB is on a cluster server. Is there an
y way to explicitly script or set this ability for SQL Server 2000? Thanks.Hi Journika
Database role membership is only stored in the database itself. So once the
database is offline, there is no way to know who is in the db_owner role of
the offline database. Bringing the db back online will have to be done by
someone with privilege at the server level, or by the true owner of the
database, as listed in sysdatabses (and viewed through sp_helpdb)
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Journika" <anonymous@.discussions.microsoft.com> wrote in message
news:3CFB7F32-C517-4818-8AEC-7A9B135F3017@.microsoft.com...
> I have a user with db_owner status who can take a DB offline, but for some
reason can't bring it back online. The DB is on a cluster server. Is there
any way to explicitly script or set this ability for SQL Server 2000?
Thanks.

dbmssocn bug?

sometimes, if I connect DNS name for localhost running sql2000, (go to the
router and back) at a simple "SELECT * FROM table" statament I get a long
delay (application hangs for 10-20 second), and drops the connection.
When I change the datasource to "netbios" name, the same statament works
without trouble.
where is the bug? In dbmssocn? in ADO events (I use them...)?
cursorlocations? Why only sometimes?
What did you mean use DNS name and NetBIOS name ?
Are you connecting from a client PC? Does it work with Query Analyser ? Does
it timeout all the time.
"SRINGER Zoltn" <kecskemetisrac@.free-mail.hu> wrote in message
news:O7hVZOiBFHA.3840@.tk2msftngp13.phx.gbl...
> sometimes, if I connect DNS name for localhost running sql2000, (go to the
> router and back) at a simple "SELECT * FROM table" statament I get a long
> delay (application hangs for 10-20 second), and drops the connection.
> When I change the datasource to "netbios" name, the same statament works
> without trouble.
> where is the bug? In dbmssocn? in ADO events (I use them...)?
> cursorlocations? Why only sometimes?
>
|||another relevant information:
if I change cursorlocation to adUseClient, works...
... but I need serverside cursor especially via internet!
|||From the earlier posts, it sounds like you are could just
have some DNS issues in your network. Have you checked the
event logs for such? Have you tried an alias using the IP
address?
-Sue
On Mon, 31 Jan 2005 16:13:33 +0100, "SRINGER Zoltn"
<kecskemetisrac@.free-mail.hu> wrote:

>another relevant information:
>if I change cursorlocation to adUseClient, works...
>
>... but I need serverside cursor especially via internet!
>

dbmssocn bug?

sometimes, if I connect DNS name for localhost running sql2000, (go to the
router and back) at a simple "SELECT * FROM table" statament I get a long
delay (application hangs for 10-20 second), and drops the connection.
When I change the datasource to "netbios" name, the same statament works
without trouble.
where is the bug? In dbmssocn? in ADO events (I use them...)?
cursorlocations? Why only sometimes?What did you mean use DNS name and NetBIOS name ?
Are you connecting from a client PC? Does it work with Query Analyser ? Does
it timeout all the time.
"SRINGER Zoltn" <kecskemetisrac@.free-mail.hu> wrote in message
news:O7hVZOiBFHA.3840@.tk2msftngp13.phx.gbl...
> sometimes, if I connect DNS name for localhost running sql2000, (go to the
> router and back) at a simple "SELECT * FROM table" statament I get a long
> delay (application hangs for 10-20 second), and drops the connection.
> When I change the datasource to "netbios" name, the same statament works
> without trouble.
> where is the bug? In dbmssocn? in ADO events (I use them...)?
> cursorlocations? Why only sometimes?
>|||another relevant information:
if I change cursorlocation to adUseClient, works...
... but I need serverside cursor especially via internet!|||From the earlier posts, it sounds like you are could just
have some DNS issues in your network. Have you checked the
event logs for such? Have you tried an alias using the IP
address?
-Sue
On Mon, 31 Jan 2005 16:13:33 +0100, "SRINGER Zoltn"
<kecskemetisrac@.free-mail.hu> wrote:

>another relevant information:
>if I change cursorlocation to adUseClient, works...
>
>... but I need serverside cursor especially via internet!
>