Options
SQL Query Fragment
Rhys
Posts: 35
Hi,
In the deadlock event often I see the language event as something like...
"Language Event: (@p0 datetime,@p1 int,@p2 int,@p3 int,@p4 int,@p5 int,@p6 int,@p7 int,@p8 int,@p9 int,@p10 int,@p11 int,@p12 int,@p13 int,@p14 int,@p15 int,@p16 int,@p17 int,@p18 int,@p19 int,@p20 int,@p21 int,@p22 int,@p23 int,@p24 int,@p25 int,@p26 int,@p27 int,@p28 in"
Not particulary useful for troubleshooting. Is it possible to capture the entire statement?
Cheers,
Rhys
In the deadlock event often I see the language event as something like...
"Language Event: (@p0 datetime,@p1 int,@p2 int,@p3 int,@p4 int,@p5 int,@p6 int,@p7 int,@p8 int,@p9 int,@p10 int,@p11 int,@p12 int,@p13 int,@p14 int,@p15 int,@p16 int,@p17 int,@p18 int,@p19 int,@p20 int,@p21 int,@p22 int,@p23 int,@p24 int,@p25 int,@p26 int,@p27 int,@p28 in"
Not particulary useful for troubleshooting. Is it possible to capture the entire statement?
Cheers,
Rhys
Comments
This is very likely a limitation of the trace flag (1204) we currently set to obtain deadlock information from the sql server error log. We will be reviewing this for v3.0.
http://www.red-gate.com/MessageBoard/vi ... hp?t=12886
Regards
Chris
Test Engineer
Red Gate