deadlocks after dbcc checkdb

sql2k sp3
Over the weekend I had severe corruption and needed to do DBCC with
repair_allow_data_loss. Since then Ive had tons of deadlocks on lots of
different tables. Any ideas as to why? I know I can trace them and figure
them out, but I was curious as to why this would start to happen after my
problems?
TIA, ChrisR.
The only thing I can think of is that the repair dropped some pages. The
data now resides on fewer pages, fewer pages with the same number of locks =
deadlock..
The problem with this thinking is that I do not know if DBCC repair moves
rows or simply drops bad page links..
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"ChrisR" <noemail@.bla.com> wrote in message
news:uA12OEBUFHA.3644@.TK2MSFTNGP10.phx.gbl...
> sql2k sp3
> Over the weekend I had severe corruption and needed to do DBCC with
> repair_allow_data_loss. Since then Ive had tons of deadlocks on lots of
> different tables. Any ideas as to why? I know I can trace them and figure
> them out, but I was curious as to why this would start to happen after my
> problems?
> TIA, ChrisR.
>
|||How about if repair removed a whole index in order to repair? That could increase deadlock due to
longer execution time = overlap. Or? I don't know whether repair does drop a whole index, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eRZ6oeBUFHA.2172@.tk2msftngp13.phx.gbl...
> The only thing I can think of is that the repair dropped some pages. The
> data now resides on fewer pages, fewer pages with the same number of locks =
> deadlock..
> The problem with this thinking is that I do not know if DBCC repair moves
> rows or simply drops bad page links..
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "ChrisR" <noemail@.bla.com> wrote in message
> news:uA12OEBUFHA.3644@.TK2MSFTNGP10.phx.gbl...
>
|||Assuming you're on SQL 2000, repair won't drop whole indexes (only rebuild
them) or do anything that would cause deadlocks. However, it probably had to
delete some pages so whatever application logic was inherent in the database
is now broken (i.e. if your app relied on certain values being present in
multiple tables, that may not be the case any more).
Did you study the output of repair to work out roughly what it dropped? I
take it your backup was broken too which is why you had to run repair rather
than restoring your backup? Did you work out why the corruption happened in
the first place so you can ensure it doesn't happen again?
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ecDwqnBUFHA.2928@.TK2MSFTNGP09.phx.gbl...
> How about if repair removed a whole index in order to repair? That could
increase deadlock due to
> longer execution time = overlap. Or? I don't know whether repair does drop
a whole index, though...[vbcol=seagreen]
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
> news:eRZ6oeBUFHA.2172@.tk2msftngp13.phx.gbl...
locks =[vbcol=seagreen]
moves[vbcol=seagreen]
figure[vbcol=seagreen]
my
>
|||Hardware issues were the cause. Yes the backups were bad. MS is now
evaluating the output. Thanks to all who helped.
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:OXOmsFPUFHA.1148@.tk2msftngp13.phx.gbl...
> Assuming you're on SQL 2000, repair won't drop whole indexes (only rebuild
> them) or do anything that would cause deadlocks. However, it probably had
> to
> delete some pages so whatever application logic was inherent in the
> database
> is now broken (i.e. if your app relied on certain values being present in
> multiple tables, that may not be the case any more).
> Did you study the output of repair to work out roughly what it dropped? I
> take it your backup was broken too which is why you had to run repair
> rather
> than restoring your backup? Did you work out why the corruption happened
> in
> the first place so you can ensure it doesn't happen again?
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in
> message news:ecDwqnBUFHA.2928@.TK2MSFTNGP09.phx.gbl...
> increase deadlock due to
> a whole index, though...
> locks =
> moves
> figure
> my
>

deadlocks after dbcc checkdb

sql2k sp3
Over the weekend I had severe corruption and needed to do DBCC with
repair_allow_data_loss. Since then Ive had tons of deadlocks on lots of
different tables. Any ideas as to why? I know I can trace them and figure
them out, but I was curious as to why this would start to happen after my
problems?
TIA, ChrisR.The only thing I can think of is that the repair dropped some pages. The
data now resides on fewer pages, fewer pages with the same number of locks =deadlock..
The problem with this thinking is that I do not know if DBCC repair moves
rows or simply drops bad page links..
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"ChrisR" <noemail@.bla.com> wrote in message
news:uA12OEBUFHA.3644@.TK2MSFTNGP10.phx.gbl...
> sql2k sp3
> Over the weekend I had severe corruption and needed to do DBCC with
> repair_allow_data_loss. Since then Ive had tons of deadlocks on lots of
> different tables. Any ideas as to why? I know I can trace them and figure
> them out, but I was curious as to why this would start to happen after my
> problems?
> TIA, ChrisR.
>|||How about if repair removed a whole index in order to repair? That could increase deadlock due to
longer execution time = overlap. Or? I don't know whether repair does drop a whole index, though...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eRZ6oeBUFHA.2172@.tk2msftngp13.phx.gbl...
> The only thing I can think of is that the repair dropped some pages. The
> data now resides on fewer pages, fewer pages with the same number of locks => deadlock..
> The problem with this thinking is that I do not know if DBCC repair moves
> rows or simply drops bad page links..
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "ChrisR" <noemail@.bla.com> wrote in message
> news:uA12OEBUFHA.3644@.TK2MSFTNGP10.phx.gbl...
>> sql2k sp3
>> Over the weekend I had severe corruption and needed to do DBCC with
>> repair_allow_data_loss. Since then Ive had tons of deadlocks on lots of
>> different tables. Any ideas as to why? I know I can trace them and figure
>> them out, but I was curious as to why this would start to happen after my
>> problems?
>> TIA, ChrisR.
>>
>|||Assuming you're on SQL 2000, repair won't drop whole indexes (only rebuild
them) or do anything that would cause deadlocks. However, it probably had to
delete some pages so whatever application logic was inherent in the database
is now broken (i.e. if your app relied on certain values being present in
multiple tables, that may not be the case any more).
Did you study the output of repair to work out roughly what it dropped? I
take it your backup was broken too which is why you had to run repair rather
than restoring your backup? Did you work out why the corruption happened in
the first place so you can ensure it doesn't happen again?
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ecDwqnBUFHA.2928@.TK2MSFTNGP09.phx.gbl...
> How about if repair removed a whole index in order to repair? That could
increase deadlock due to
> longer execution time = overlap. Or? I don't know whether repair does drop
a whole index, though...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
> news:eRZ6oeBUFHA.2172@.tk2msftngp13.phx.gbl...
> > The only thing I can think of is that the repair dropped some pages. The
> > data now resides on fewer pages, fewer pages with the same number of
locks => > deadlock..
> >
> > The problem with this thinking is that I do not know if DBCC repair
moves
> > rows or simply drops bad page links..
> >
> >
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > (Please respond only to the newsgroup.)
> >
> > I support the Professional Association for SQL Server ( PASS) and it's
> > community of SQL Professionals.
> > "ChrisR" <noemail@.bla.com> wrote in message
> > news:uA12OEBUFHA.3644@.TK2MSFTNGP10.phx.gbl...
> >> sql2k sp3
> >>
> >> Over the weekend I had severe corruption and needed to do DBCC with
> >> repair_allow_data_loss. Since then Ive had tons of deadlocks on lots of
> >> different tables. Any ideas as to why? I know I can trace them and
figure
> >> them out, but I was curious as to why this would start to happen after
my
> >> problems?
> >>
> >> TIA, ChrisR.
> >>
> >>
> >
> >
>|||Hardware issues were the cause. Yes the backups were bad. MS is now
evaluating the output. Thanks to all who helped.
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:OXOmsFPUFHA.1148@.tk2msftngp13.phx.gbl...
> Assuming you're on SQL 2000, repair won't drop whole indexes (only rebuild
> them) or do anything that would cause deadlocks. However, it probably had
> to
> delete some pages so whatever application logic was inherent in the
> database
> is now broken (i.e. if your app relied on certain values being present in
> multiple tables, that may not be the case any more).
> Did you study the output of repair to work out roughly what it dropped? I
> take it your backup was broken too which is why you had to run repair
> rather
> than restoring your backup? Did you work out why the corruption happened
> in
> the first place so you can ensure it doesn't happen again?
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in
> message news:ecDwqnBUFHA.2928@.TK2MSFTNGP09.phx.gbl...
>> How about if repair removed a whole index in order to repair? That could
> increase deadlock due to
>> longer execution time = overlap. Or? I don't know whether repair does
>> drop
> a whole index, though...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
>> news:eRZ6oeBUFHA.2172@.tk2msftngp13.phx.gbl...
>> > The only thing I can think of is that the repair dropped some pages.
>> > The
>> > data now resides on fewer pages, fewer pages with the same number of
> locks =>> > deadlock..
>> >
>> > The problem with this thinking is that I do not know if DBCC repair
> moves
>> > rows or simply drops bad page links..
>> >
>> >
>> > --
>> > Wayne Snyder MCDBA, SQL Server MVP
>> > Mariner, Charlotte, NC
>> > (Please respond only to the newsgroup.)
>> >
>> > I support the Professional Association for SQL Server ( PASS) and it's
>> > community of SQL Professionals.
>> > "ChrisR" <noemail@.bla.com> wrote in message
>> > news:uA12OEBUFHA.3644@.TK2MSFTNGP10.phx.gbl...
>> >> sql2k sp3
>> >>
>> >> Over the weekend I had severe corruption and needed to do DBCC with
>> >> repair_allow_data_loss. Since then Ive had tons of deadlocks on lots
>> >> of
>> >> different tables. Any ideas as to why? I know I can trace them and
> figure
>> >> them out, but I was curious as to why this would start to happen after
> my
>> >> problems?
>> >>
>> >> TIA, ChrisR.
>> >>
>> >>
>> >
>> >
>>
>

deadlocks after dbcc checkdb

sql2k sp3
Over the weekend I had severe corruption and needed to do DBCC with
repair_allow_data_loss. Since then Ive had tons of deadlocks on lots of
different tables. Any ideas as to why? I know I can trace them and figure
them out, but I was curious as to why this would start to happen after my
problems?
TIA, ChrisR.The only thing I can think of is that the repair dropped some pages. The
data now resides on fewer pages, fewer pages with the same number of locks =
deadlock..
The problem with this thinking is that I do not know if DBCC repair moves
rows or simply drops bad page links..
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"ChrisR" <noemail@.bla.com> wrote in message
news:uA12OEBUFHA.3644@.TK2MSFTNGP10.phx.gbl...
> sql2k sp3
> Over the weekend I had severe corruption and needed to do DBCC with
> repair_allow_data_loss. Since then Ive had tons of deadlocks on lots of
> different tables. Any ideas as to why? I know I can trace them and figure
> them out, but I was curious as to why this would start to happen after my
> problems?
> TIA, ChrisR.
>|||How about if repair removed a whole index in order to repair? That could inc
rease deadlock due to
longer execution time = overlap. Or? I don't know whether repair does drop a
whole index, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eRZ6oeBUFHA.2172@.tk2msftngp13.phx.gbl...
> The only thing I can think of is that the repair dropped some pages. The
> data now resides on fewer pages, fewer pages with the same number of locks
=
> deadlock..
> The problem with this thinking is that I do not know if DBCC repair moves
> rows or simply drops bad page links..
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "ChrisR" <noemail@.bla.com> wrote in message
> news:uA12OEBUFHA.3644@.TK2MSFTNGP10.phx.gbl...
>|||Assuming you're on SQL 2000, repair won't drop whole indexes (only rebuild
them) or do anything that would cause deadlocks. However, it probably had to
delete some pages so whatever application logic was inherent in the database
is now broken (i.e. if your app relied on certain values being present in
multiple tables, that may not be the case any more).
Did you study the output of repair to work out roughly what it dropped? I
take it your backup was broken too which is why you had to run repair rather
than restoring your backup? Did you work out why the corruption happened in
the first place so you can ensure it doesn't happen again?
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ecDwqnBUFHA.2928@.TK2MSFTNGP09.phx.gbl...
> How about if repair removed a whole index in order to repair? That could
increase deadlock due to
> longer execution time = overlap. Or? I don't know whether repair does drop
a whole index, though...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
> news:eRZ6oeBUFHA.2172@.tk2msftngp13.phx.gbl...
locks =[vbcol=seagreen]
moves[vbcol=seagreen]
figure[vbcol=seagreen]
my[vbcol=seagreen]
>|||Hardware issues were the cause. Yes the backups were bad. MS is now
evaluating the output. Thanks to all who helped.
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:OXOmsFPUFHA.1148@.tk2msftngp13.phx.gbl...
> Assuming you're on SQL 2000, repair won't drop whole indexes (only rebuild
> them) or do anything that would cause deadlocks. However, it probably had
> to
> delete some pages so whatever application logic was inherent in the
> database
> is now broken (i.e. if your app relied on certain values being present in
> multiple tables, that may not be the case any more).
> Did you study the output of repair to work out roughly what it dropped? I
> take it your backup was broken too which is why you had to run repair
> rather
> than restoring your backup? Did you work out why the corruption happened
> in
> the first place so you can ensure it doesn't happen again?
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in
> message news:ecDwqnBUFHA.2928@.TK2MSFTNGP09.phx.gbl...
> increase deadlock due to
> a whole index, though...
> locks =
> moves
> figure
> my
>sql

deadlock info

Is there a way to tell which two process' were involved in a deadlck after
it happens?
--
SQL2K SP3
TIA, ChrisRChrisR wrote:
> Is there a way to tell which two process' were involved in a deadlck
> after it happens?
Not after. You can run profiler and trap the deadlock and deadlock chain
events. But you'll need to add the proper SQL event to really see what
was going on. At the very least, you'll need SQL:BatchStarting and
RPC:Starting. better would be to add SQL:StmtStarting for SQL and
SP:StmtStarting for SPs.
--
David Gugick
Imceda Software
www.imceda.com|||You can if you're running the output of trace flag 1204 for all connections
to the SQL log.
To do this, issue the following command:
DBCC TRACEON (3605, 1204, -1)
When a deadlock occurs, you'll get a detailed report on the processes, what
objects were locked etc. It's tricky to decipher the output of this trace
flag at first but if you have difficulty post the output back here & I'm
you'll get plenty of help.
Regards,
Greg Linwood
SQL Server MVP
"ChrisR" <bla@.noemail.com> wrote in message
news:OT6gtSozEHA.2568@.TK2MSFTNGP10.phx.gbl...
> Is there a way to tell which two process' were involved in a deadlck after
> it happens?
> --
> SQL2K SP3
> TIA, ChrisR
>

deadlock alert

sql2k sp3
I want to have an alert email me whenever a deadlock occurs. SQLMail is
working properly. I create an alert and specify Error 1205. Then I specify
myself in the email section. Then I purposely cause a deadlock but never get
emailed. In addition to this, the deadlock never goes in the TLog either. An
y
ideas?
TIA, ChrisRDid you select "Always write to Windows Eventlog" for error 1205?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
> sql2k sp3
> I want to have an alert email me whenever a deadlock occurs. SQLMail is
> working properly. I create an alert and specify Error 1205. Then I specify
> myself in the email section. Then I purposely cause a deadlock but never g
et
> emailed. In addition to this, the deadlock never goes in the TLog either.
Any
> ideas?
>
> TIA, ChrisR|||I don't see that as an option anywhere. Will this help my email/ TLog proble
m?
"Tibor Karaszi" wrote:

> Did you select "Always write to Windows Eventlog" for error 1205?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
>
>|||Where would I check this at?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:udq$65JsEHA.2212@.TK2MSFTNGP14.phx.gbl...
> Did you select "Always write to Windows Eventlog" for error 1205?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
specify[vbcol=seagreen]
get[vbcol=seagreen]
either. Any[vbcol=seagreen]
>|||EM, right-click the server, Manage SQL Server Messages, search your message
in this dialog.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <chris@.noemail.com> wrote in message news:%230t$w4MsEHA.3320@.TK2MSFTNGP15.phx.gbl..
.
> Where would I check this at?
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:udq$65JsEHA.2212@.TK2MSFTNGP14.phx.gbl...
> specify
> get
> either. Any
>

deadlock alert

sql2k sp3
I want to have an alert email me whenever a deadlock occurs. SQLMail is
working properly. I create an alert and specify Error 1205. Then I specify
myself in the email section. Then I purposely cause a deadlock but never get
emailed. In addition to this, the deadlock never goes in the TLog either. Any
ideas?
TIA, ChrisRDid you select "Always write to Windows Eventlog" for error 1205?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
> sql2k sp3
> I want to have an alert email me whenever a deadlock occurs. SQLMail is
> working properly. I create an alert and specify Error 1205. Then I specify
> myself in the email section. Then I purposely cause a deadlock but never get
> emailed. In addition to this, the deadlock never goes in the TLog either. Any
> ideas?
>
> TIA, ChrisR|||I don't see that as an option anywhere. Will this help my email/ TLog problem?
"Tibor Karaszi" wrote:
> Did you select "Always write to Windows Eventlog" for error 1205?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
> > sql2k sp3
> >
> > I want to have an alert email me whenever a deadlock occurs. SQLMail is
> > working properly. I create an alert and specify Error 1205. Then I specify
> > myself in the email section. Then I purposely cause a deadlock but never get
> > emailed. In addition to this, the deadlock never goes in the TLog either. Any
> > ideas?
> >
> >
> > TIA, ChrisR
>
>|||Where would I check this at?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:udq$65JsEHA.2212@.TK2MSFTNGP14.phx.gbl...
> Did you select "Always write to Windows Eventlog" for error 1205?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
> > sql2k sp3
> >
> > I want to have an alert email me whenever a deadlock occurs. SQLMail is
> > working properly. I create an alert and specify Error 1205. Then I
specify
> > myself in the email section. Then I purposely cause a deadlock but never
get
> > emailed. In addition to this, the deadlock never goes in the TLog
either. Any
> > ideas?
> >
> >
> > TIA, ChrisR
>|||EM, right-click the server, Manage SQL Server Messages, search your message in this dialog.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <chris@.noemail.com> wrote in message news:%230t$w4MsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> Where would I check this at?
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:udq$65JsEHA.2212@.TK2MSFTNGP14.phx.gbl...
>> Did you select "Always write to Windows Eventlog" for error 1205?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
>> news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
>> > sql2k sp3
>> >
>> > I want to have an alert email me whenever a deadlock occurs. SQLMail is
>> > working properly. I create an alert and specify Error 1205. Then I
> specify
>> > myself in the email section. Then I purposely cause a deadlock but never
> get
>> > emailed. In addition to this, the deadlock never goes in the TLog
> either. Any
>> > ideas?
>> >
>> >
>> > TIA, ChrisR
>>
>

deadlock alert

sql2k sp3
I want to have an alert email me whenever a deadlock occurs. SQLMail is
working properly. I create an alert and specify Error 1205. Then I specify
myself in the email section. Then I purposely cause a deadlock but never get
emailed. In addition to this, the deadlock never goes in the TLog either. Any
ideas?
TIA, ChrisR
Did you select "Always write to Windows Eventlog" for error 1205?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
> sql2k sp3
> I want to have an alert email me whenever a deadlock occurs. SQLMail is
> working properly. I create an alert and specify Error 1205. Then I specify
> myself in the email section. Then I purposely cause a deadlock but never get
> emailed. In addition to this, the deadlock never goes in the TLog either. Any
> ideas?
>
> TIA, ChrisR
|||I don't see that as an option anywhere. Will this help my email/ TLog problem?
"Tibor Karaszi" wrote:

> Did you select "Always write to Windows Eventlog" for error 1205?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
>
>
|||Where would I check this at?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:udq$65JsEHA.2212@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> Did you select "Always write to Windows Eventlog" for error 1205?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:01EDCE91-12E5-4DD6-9C13-C5CDA5BE3D20@.microsoft.com...
specify[vbcol=seagreen]
get[vbcol=seagreen]
either. Any
>
|||EM, right-click the server, Manage SQL Server Messages, search your message in this dialog.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <chris@.noemail.com> wrote in message news:%230t$w4MsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> Where would I check this at?
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:udq$65JsEHA.2212@.TK2MSFTNGP14.phx.gbl...
> specify
> get
> either. Any
>