--=_NextPart_000_0009_01C42850.46616820
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I'm receiving this in my SQL server event log. Although I have trace = flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) = Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have = SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_0009_01C42850.46616820
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I'm receiving this in my SQL server = event log. Although I have trace flag 2004 enabled, this is all that I see in = the SQL log.
Victim Resource = Owner: ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have = SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have any = suggestions for how to address this?
--=_NextPart_000_0009_01C42850.46616820--I'm no expert on the log entry, but the word 'Victim' suggests to me that
this is not a deadlock, since SQL Server has chosen one of the transactions
as victim?
"ET" <et@.et.com> wrote in message
news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have trace flag
2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098)
Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?|||This is a multi-part message in MIME format.
--=_NextPart_000_0061_01C4284F.80380960
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
ET,
What made you work with hotfix build 840? With hotfix builds you can =never be sure what you are getting.
Chris Wood
Alberta Department of Energy
CANADA
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have trace =flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) =Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have =SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_0061_01C4284F.80380960
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
ET,
What made you work with hotfix build =840? With hotfix builds you can never be sure what you are getting.
Chris Wood
Alberta Department of =Energy
CANADA
"ET"
I'm receiving this in my SQL server =event log. Although I have trace flag 2004 enabled, this is all that I =see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have =SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have =any suggestions for how to address this?
--=_NextPart_000_0061_01C4284F.80380960--|||This is a multi-part message in MIME format.
--=_NextPart_000_0111_01C4284A.1FA2A420
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
What do you think you are getting with traceflag 2004? The flag for =trapping deadlocks is 1204. What exactly are you trying to address?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have trace =flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) =Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have =SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_0111_01C4284A.1FA2A420
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
What do you think you are getting with =traceflag 2004? The flag for trapping deadlocks is 1204.
What exactly are you trying to address?
-- HTH--Kalen DelaneySQL Server =MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I'm receiving this in my SQL server =event log. Although I have trace flag 2004 enabled, this is all that I =see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have =SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have =any suggestions for how to address this?
--=_NextPart_000_0111_01C4284A.1FA2A420--|||This is a multi-part message in MIME format.
--=_NextPart_000_003E_01C42865.2A7057B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sorry. That was a typo on my part. I meant 1204.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:#h#bTTIKEHA.2716@.tk2msftngp13.phx.gbl...
What do you think you are getting with traceflag 2004? The flag for =trapping deadlocks is 1204. What exactly are you trying to address?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have trace =flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) =Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I =have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_003E_01C42865.2A7057B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Sorry. That was a typo on my part. I =meant 1204.
"Kalen Delaney"
What do you think you are getting =with traceflag 2004? The flag for trapping deadlocks is 1204.
What exactly are you trying to address?
-- HTH--Kalen DelaneySQL Server = MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I'm receiving this in my SQL server =event log. Although I have trace flag 2004 enabled, this is all that I =see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have any suggestions for how to address this?
--=_NextPart_000_003E_01C42865.2A7057B0--|||This is a multi-part message in MIME format.
--=_NextPart_000_0044_01C42865.7EDCBD20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
It was given to me by Microsoft some time ago to resolve an issue we =were having at the time.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message =news:ORk$LHIKEHA.2888@.TK2MSFTNGP09.phx.gbl...
ET,
What made you work with hotfix build 840? With hotfix builds you can =never be sure what you are getting.
Chris Wood
Alberta Department of Energy
CANADA
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have trace =flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) =Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I =have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_0044_01C42865.7EDCBD20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
It was given to me by Microsoft some =time ago to resolve an issue we were having at the time.
"Chris Wood" wrote in message news:ORk$LHIKEHA.2888=@.TK2MSFTNGP09.phx.gbl...
ET,
What made you work with hotfix build =840? With hotfix builds you can never be sure what you are getting.
Chris Wood
Alberta Department of =Energy
CANADA
"ET"
I'm receiving this in my SQL server =event log. Although I have trace flag 2004 enabled, this is all that I =see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I have SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have any suggestions for how to address this?
--=_NextPart_000_0044_01C42865.7EDCBD20--|||This is a multi-part message in MIME format.
--=_NextPart_000_008E_01C4285C.70769B60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
You must be using replication.
Chris
"ET" <et@.et.com> wrote in message =news:%23ZgYHcIKEHA.3592@.TK2MSFTNGP09.phx.gbl...
It was given to me by Microsoft some time ago to resolve an issue we =were having at the time.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message =news:ORk$LHIKEHA.2888@.TK2MSFTNGP09.phx.gbl...
ET,
What made you work with hotfix build 840? With hotfix builds you can =never be sure what you are getting.
Chris Wood
Alberta Department of Energy
CANADA
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have =trace flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) =Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I =have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_008E_01C4285C.70769B60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>You must be using =replication.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Chris</FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"ET" <<A href=3D"mailto:et@.et.com">et@.et.com</A>> wrote in =message <A =href=3D"news:%23ZgYHcIKEHA.3592@.TK2MSFTNGP09.phx.gbl">news:%23ZgYHcIKEHA.=3592@.TK2MSFTNGP09.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>It was given to me by Microsoft some =time ago to resolve an issue we were having at the time.</FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Chris Wood" <<A =href=3D"mailto:anonymous@.discussions.microsoft.com">anonymous@.discussions=.microsoft.com</A>> wrote in message <A =href=3D"news:ORk$LHIKEHA.2888@.TK2MSFTNGP09.phx.gbl">news:ORk$LHIKEHA.2888=@.TK2MSFTNGP09.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>ET,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>What made you work with hotfix =build 840? With hotfix builds you can never be sure what you are =getting.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Chris Wood</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Alberta Department of =Energy</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>CANADA</FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"ET" <<A href=3D"mailto:et@.et.com">et@.et.com</A>> wrote =in message <A =href=3D"news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl">news:e2wuOHHKEHA.3944=@.tk2msftngp13.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'm receiving this in my SQL =server event log. Although I have trace flag 2004 enabled, this is all that I see in the SQL log.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Victim Resource Owner:<BR> ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2></FONT></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =size=3D3>I am running SQL 2000, build 840, on Windows server 2003. Also, I have SQL<BR>configured to use 14GB from a total of 16GB on the server.<BR><BR>Does anyone have any suggestions for how to address =
this?</FONT><BR></DIV>
=<DIV><BR><BR></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></FONT></BODY><=/HTML>
--=_NextPart_000_008E_01C4285C.70769B60--|||This is a multi-part message in MIME format.
--=_NextPart_000_0082_01C4286E.7E3DA7E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
No
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message =news:u4yS86IKEHA.1388@.TK2MSFTNGP09.phx.gbl...
You must be using replication.
Chris
"ET" <et@.et.com> wrote in message =news:%23ZgYHcIKEHA.3592@.TK2MSFTNGP09.phx.gbl...
It was given to me by Microsoft some time ago to resolve an issue we =were having at the time.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in =message news:ORk$LHIKEHA.2888@.TK2MSFTNGP09.phx.gbl...
ET,
What made you work with hotfix build 840? With hotfix builds you =can never be sure what you are getting.
Chris Wood
Alberta Department of Energy
CANADA
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have =trace flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) =Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, =I have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_0082_01C4286E.7E3DA7E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
No
"Chris Wood" wrote in message news:u4yS86IKEHA.1388=@.TK2MSFTNGP09.phx.gbl...
You must be using =replication.
Chris
"ET"
It was given to me by Microsoft =some time ago to resolve an issue we were having at the time.
"Chris Wood" wrote in message news:ORk$LHIKEHA.2888=@.TK2MSFTNGP09.phx.gbl...
ET,
What made you work with hotfix =build 840? With hotfix builds you can never be sure what you are getting.
Chris Wood
Alberta Department of =Energy
CANADA
"ET"
I'm receiving this in my SQL =server event log. Although I have trace flag 2004 enabled, this is all that I = see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I =have SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have any suggestions for how to =address this?
=
--=_NextPart_000_0082_01C4286E.7E3DA7E0--|||This is a multi-part message in MIME format.
--=_NextPart_000_00A8_01C4285C.1BA6B930
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Ok, so what are you trying to address? Do you know you have a deadlock? How? How are you checking the errorlog?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#KRAzaIKEHA.3628@.TK2MSFTNGP12.phx.gbl...
Sorry. That was a typo on my part. I meant 1204.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:#h#bTTIKEHA.2716@.tk2msftngp13.phx.gbl...
What do you think you are getting with traceflag 2004? The flag for =trapping deadlocks is 1204. What exactly are you trying to address?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have =trace flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) =Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I =have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_00A8_01C4285C.1BA6B930
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Ok, so what are you trying to address? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Do you know you have a deadlock? How? =</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>How are you checking the =errorlog?</FONT><BR>-- <BR>HTH<BR>--<BR>Kalen Delaney<BR>SQL Server MVP<BR><A href=3D"www.solidqualitylearning.com=/">http://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
</A></DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"ET" <<A href=3D"mailto:et@.et.com">et@.et.com</A>> wrote in =message <A =href=3D"news:#KRAzaIKEHA.3628@.TK2MSFTNGP12.phx.gbl">news:#KRAzaIKEHA.3628=@.TK2MSFTNGP12.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Sorry. That was a typo on my part. I =meant 1204.</FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Kalen Delaney" <<A =href=3D"mailto:replies@.public_newsgroups.com">replies@.public_newsgroups.c=om</A>> wrote in message <A =href=3D"news:#h#bTTIKEHA.2716@.tk2msftngp13.phx.gbl">news:#h#bTTIKEHA.2716=@.tk2msftngp13.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>What do you think you are getting =with traceflag 2004? The flag for trapping deadlocks is 1204. =</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>What exactly are you trying to address?</FONT></DIV>
<DIV><BR>-- <BR>HTH<BR>--<BR>Kalen Delaney<BR>SQL =Server MVP<BR><A =href=3D"www.solidqualitylearning.com=/">http://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
</A></DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"ET" <<A href=3D"mailto:et@.et.com">et@.et.com</A>> wrote =in message <A =href=3D"news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl">news:e2wuOHHKEHA.3944=@.tk2msftngp13.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'm receiving this in my SQL =server event log. Although I have trace flag 2004 enabled, this is all that I see in the SQL log.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Victim Resource Owner:<BR> ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2></FONT></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =size=3D3>I am running SQL 2000, build 840, on Windows server 2003. Also, I have SQL<BR>configured to use 14GB from a total of 16GB on the server.<BR><BR>Does anyone have any suggestions for how to address =
this?</FONT><BR></DIV>
=<DIV><BR><BR></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></FONT></BODY><=/HTML>
--=_NextPart_000_00A8_01C4285C.1BA6B930--|||This is a multi-part message in MIME format.
--=_NextPart_000_00B4_01C4287E.EC873210
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I was reading the errorlog using xp_readerrorlog when I noticed thse =entries.
I am trying to determine if this is some type of undetected deadlock =that may be degrading performance in some way.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:esu8SbJKEHA.3920@.TK2MSFTNGP10.phx.gbl...
Ok, so what are you trying to address? Do you know you have a deadlock? How? How are you checking the errorlog?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#KRAzaIKEHA.3628@.TK2MSFTNGP12.phx.gbl...
Sorry. That was a typo on my part. I meant 1204.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:#h#bTTIKEHA.2716@.tk2msftngp13.phx.gbl...
What do you think you are getting with traceflag 2004? The flag =for trapping deadlocks is 1204. What exactly are you trying to address?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have =trace flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) =Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, =I have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_00B4_01C4287E.EC873210
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I was reading the errorlog using =xp_readerrorlog when I noticed thse entries.
I am trying to determine if this is =some type of undetected deadlock that may be degrading performance in some =way.
"Kalen Delaney"
Ok, so what are you trying to =address?
Do you know you have a deadlock? How? =
How are you checking the =errorlog?-- HTH--Kalen DelaneySQL Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
Sorry. That was a typo on my part. =I meant 1204.
"Kalen Delaney"
What do you think you are getting =with traceflag 2004? The flag for trapping deadlocks is 1204. = What exactly are you trying to address?
-- HTH--Kalen DelaneySQL =Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I'm receiving this in my SQL =server event log. Although I have trace flag 2004 enabled, this is all that I = see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I =have SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have any suggestions for how to =address this?
=
--=_NextPart_000_00B4_01C4287E.EC873210--|||This is a multi-part message in MIME format.
--=_NextPart_000_01E0_01C42874.FD574990
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Why don't you just open up the errorlog in notepad and see if there is =more?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#aq00BKKEHA.2024@.TK2MSFTNGP11.phx.gbl...
I was reading the errorlog using xp_readerrorlog when I noticed thse =entries.
I am trying to determine if this is some type of undetected deadlock =that may be degrading performance in some way.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:esu8SbJKEHA.3920@.TK2MSFTNGP10.phx.gbl...
Ok, so what are you trying to address? Do you know you have a deadlock? How? How are you checking the errorlog?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#KRAzaIKEHA.3628@.TK2MSFTNGP12.phx.gbl...
Sorry. That was a typo on my part. I meant 1204.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:#h#bTTIKEHA.2716@.tk2msftngp13.phx.gbl...
What do you think you are getting with traceflag 2004? The flag =for trapping deadlocks is 1204. What exactly are you trying to address?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I have =trace flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 =Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. =Also, I have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_01E0_01C42874.FD574990
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Why don't you just open up the errorlog =in notepad and see if there is more?
-- HTH--Kalen DelaneySQL Server =MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I was reading the errorlog using =xp_readerrorlog when I noticed thse entries.
I am trying to determine if this is =some type of undetected deadlock that may be degrading performance in some way.
"Kalen Delaney"
Ok, so what are you trying to =address?
Do you know you have a deadlock? =How?
How are you checking the =errorlog?-- HTH--Kalen DelaneySQL Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
Sorry. That was a typo on my =part. I meant 1204.
"Kalen Delaney"
What do you think you are =getting with traceflag 2004? The flag for trapping deadlocks is 1204. = What exactly are you trying to address?
-- HTH--Kalen DelaneySQL =Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I'm receiving this in my SQL =server event log. Although I have trace flag 2004 enabled, this is all that =I see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 =ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. Also, I =have SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have any suggestions for how to =address this?
=
--=_NextPart_000_01E0_01C42874.FD574990--|||This is a multi-part message in MIME format.
--=_NextPart_000_000B_01C428FF.EE350480
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
There is no more. That's my point. Whether I look at it using =xp_readerrorlog or notepad, the only 2 events happening at that point in =time are the ones I listed.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:#n#g4#KKEHA.3728@.TK2MSFTNGP12.phx.gbl...
Why don't you just open up the errorlog in notepad and see if there is =more?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#aq00BKKEHA.2024@.TK2MSFTNGP11.phx.gbl...
I was reading the errorlog using xp_readerrorlog when I noticed thse =entries.
I am trying to determine if this is some type of undetected deadlock =that may be degrading performance in some way.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:esu8SbJKEHA.3920@.TK2MSFTNGP10.phx.gbl...
Ok, so what are you trying to address? Do you know you have a deadlock? How? How are you checking the errorlog?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#KRAzaIKEHA.3628@.TK2MSFTNGP12.phx.gbl...
Sorry. That was a typo on my part. I meant 1204.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in =message news:#h#bTTIKEHA.2716@.tk2msftngp13.phx.gbl...
What do you think you are getting with traceflag 2004? The =flag for trapping deadlocks is 1204. What exactly are you trying to address?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I =have trace flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 =Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. =Also, I have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_000B_01C428FF.EE350480
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
There is no more. That's my point. =Whether I look at it using xp_readerrorlog or notepad, the only 2 events happening =at that point in time are the ones I listed.
"Kalen Delaney"
Why don't you just open up the =errorlog in notepad and see if there is more?
-- HTH--Kalen DelaneySQL Server = MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I was reading the errorlog using xp_readerrorlog when I noticed thse entries.
I am trying to determine if this is =some type of undetected deadlock that may be degrading performance in some way.
"Kalen Delaney"
Ok, so what are you trying to =address?
Do you know you have a deadlock? =How?
How are you checking the errorlog?-- HTH--Kalen =DelaneySQL Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
Sorry. That was a typo on my =part. I meant 1204.
"Kalen Delaney"
What do you think you are =getting with traceflag 2004? The flag for trapping deadlocks is 1204. = What exactly are you trying =to address?
-- HTH--Kalen =DelaneySQL Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I'm receiving this in my =SQL server event log. Although I have trace flag 2004 enabled, this is =all that I see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 =ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. =Also, I have SQLconfigured to use 14GB from a total of 16GB on the server.Does anyone have any suggestions for how to =address this?
=
--=_NextPart_000_000B_01C428FF.EE350480--|||This is a multi-part message in MIME format.
--=_NextPart_000_00E8_01C4291A.A9327000
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Ok, I think I get it now, not that I know what it means. So there is no =error 1205 showing up in the log? Is there any error number showing in =the log anywhere near the time of this message?
How often are these messages occurring? If they're frequent, could you =set up a trace to capture the statements being submitted?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#uHT3FSKEHA.2380@.TK2MSFTNGP09.phx.gbl...
There is no more. That's my point. Whether I look at it using =xp_readerrorlog or notepad, the only 2 events happening at that point in =time are the ones I listed.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:#n#g4#KKEHA.3728@.TK2MSFTNGP12.phx.gbl...
Why don't you just open up the errorlog in notepad and see if there =is more?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#aq00BKKEHA.2024@.TK2MSFTNGP11.phx.gbl...
I was reading the errorlog using xp_readerrorlog when I noticed =thse entries.
I am trying to determine if this is some type of undetected =deadlock that may be degrading performance in some way.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:esu8SbJKEHA.3920@.TK2MSFTNGP10.phx.gbl...
Ok, so what are you trying to address? Do you know you have a deadlock? How? How are you checking the errorlog?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#KRAzaIKEHA.3628@.TK2MSFTNGP12.phx.gbl...
Sorry. That was a typo on my part. I meant 1204.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in =message news:#h#bTTIKEHA.2716@.tk2msftngp13.phx.gbl...
What do you think you are getting with traceflag 2004? The =flag for trapping deadlocks is 1204. What exactly are you trying to address?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although I =have trace flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 =Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. =Also, I have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?
--=_NextPart_000_00E8_01C4291A.A9327000
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Ok, I think I get it now, not that I =know what it means. So there is no error 1205 showing up in the log? Is there any =error number showing in the log anywhere near the time of this =message?
How often are these =messages occurring? If they're frequent, could you set up a trace to capture the statements =being submitted?
-- HTH--Kalen DelaneySQL Server =MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
There is no more. That's my point. =Whether I look at it using xp_readerrorlog or notepad, the only 2 events =happening at that point in time are the ones I listed.
"Kalen Delaney"
Why don't you just open up the =errorlog in notepad and see if there is more?
-- HTH--Kalen DelaneySQL =Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I was reading the errorlog using xp_readerrorlog when I noticed thse entries.
I am trying to determine if this =is some type of undetected deadlock that may be degrading performance in some way.
"Kalen Delaney"
Ok, so what are you trying to =address?
Do you know you have a =deadlock? How?
How are you checking the errorlog?-- HTH--Kalen DelaneySQL Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
Sorry. That was a typo on my =part. I meant 1204.
"Kalen Delaney"
What do you think you are =getting with traceflag 2004? The flag for trapping deadlocks is 1204.
What exactly are you trying =to address?
-- HTH--Kalen =DelaneySQL Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I'm receiving this in my =SQL server event log. Although I have trace flag 2004 enabled, this =is all that I see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 =ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 =Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server 2003. =Also, I have SQLconfigured to use 14GB from a total of 16GB on =the server.Does anyone have any suggestions for how to =address this?
=
--=_NextPart_000_00E8_01C4291A.A9327000--|||This is a multi-part message in MIME format.
--=_NextPart_000_000D_01C42944.AC7ACB20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Correct, there is no error associated with this event showing up in the =log. There are literally no other events in the SQL log for 20-30 =minutes before & after this event.
This event hasn't happened since 4/21 at 9 AM. Prior to that it would =happen 2-3 times a day on most days.
Due to the spurious nature of the event, I don't want to leave a trace =running at this point.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:O5sqXVVKEHA.1144@.TK2MSFTNGP12.phx.gbl...
Ok, I think I get it now, not that I know what it means. So there is =no error 1205 showing up in the log? Is there any error number showing =in the log anywhere near the time of this message?
How often are these messages occurring? If they're frequent, could you =set up a trace to capture the statements being submitted?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#uHT3FSKEHA.2380@.TK2MSFTNGP09.phx.gbl...
There is no more. That's my point. Whether I look at it using =xp_readerrorlog or notepad, the only 2 events happening at that point in =time are the ones I listed.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message =news:#n#g4#KKEHA.3728@.TK2MSFTNGP12.phx.gbl...
Why don't you just open up the errorlog in notepad and see if =there is more?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#aq00BKKEHA.2024@.TK2MSFTNGP11.phx.gbl...
I was reading the errorlog using xp_readerrorlog when I noticed =thse entries.
I am trying to determine if this is some type of undetected =deadlock that may be degrading performance in some way.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in =message news:esu8SbJKEHA.3920@.TK2MSFTNGP10.phx.gbl...
Ok, so what are you trying to address? Do you know you have a deadlock? How? How are you checking the errorlog?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:#KRAzaIKEHA.3628@.TK2MSFTNGP12.phx.gbl...
Sorry. That was a typo on my part. I meant 1204.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in =message news:#h#bTTIKEHA.2716@.tk2msftngp13.phx.gbl...
What do you think you are getting with traceflag 2004? The =flag for trapping deadlocks is 1204. What exactly are you trying to address?
-- HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"ET" <et@.et.com> wrote in message =news:e2wuOHHKEHA.3944@.tk2msftngp13.phx.gbl...
I'm receiving this in my SQL server event log. Although =I have trace flag 2004 enabled, this is all that I see in the SQL log.
Victim Resource Owner:
ResType:ExchangeId Stype:'AND' SPID:80 ECID:175 =Ec:(0x2DD8A098) Value:0x2d5a8c98 Cost:(0/270F)
I am running SQL 2000, build 840, on Windows server =2003. Also, I have SQL
configured to use 14GB from a total of 16GB on the =server.
Does anyone have any suggestions for how to address =this?
--=_NextPart_000_000D_01C42944.AC7ACB20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Correct, there is no error associated =with this event showing up in the log. There are literally no other events in the =SQL log for 20-30 minutes before & after this event.
This event hasn't happened since 4/21 =at 9 AM. Prior to that it would happen 2-3 times a day on most days.
Due to the spurious nature of the =event, I don't want to leave a trace running at this point.
"Kalen Delaney"
Ok, I think I get it now, not that I =know what it means. So there is no error 1205 showing up in the log? Is there any =error number showing in the log anywhere near the time of this =message?
How often are these =messages occurring? If they're frequent, could you set up a trace to capture the statements =being submitted?
-- HTH--Kalen DelaneySQL Server = MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
There is no more. That's my point. =Whether I look at it using xp_readerrorlog or notepad, the only 2 events happening at that point in time are the ones I listed.
"Kalen Delaney"
Why don't you just open up the =errorlog in notepad and see if there is more?
-- HTH--Kalen DelaneySQL =Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I was reading the errorlog =using xp_readerrorlog when I noticed thse entries.
I am trying to determine if =this is some type of undetected deadlock that may be degrading performance in =some way.
"Kalen Delaney"
Ok, so what are you trying to =address?
Do you know you have a =deadlock? How?
How are you checking the errorlog?-- HTH--Kalen DelaneySQL Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
Sorry. That was a typo on =my part. I meant 1204.
"Kalen Delaney"
What do you think you are =getting with traceflag 2004? The flag for trapping deadlocks is =1204.
What exactly are you =trying to address?
-- HTH--Kalen =DelaneySQL Server MVPhttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com=
"ET"
I'm receiving this in =my SQL server event log. Although I have trace flag 2004 enabled, this =is all that I see in the SQL log.
Victim Resource Owner: ResType:ExchangeId Stype:'AND' SPID:80 =ECID:175 Ec:(0x2DD8A098) Value:0x2d5a8c98 =Cost:(0/270F)
I am running SQL 2000, build 840, on Windows =server 2003. Also, I have SQLconfigured to use 14GB from a total =of 16GB on the server.Does anyone have any suggestions =for how to address this?
=
--=_NextPart_000_000D_01C42944.AC7ACB20--
No comments:
Post a Comment