--=_NextPart_000_0008_01C34607.4962E840
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
My boss and I are in disagreement about the Query Governor setting. Can someone please tell me if the Query Governor is set to 300, how many = minutes this translates to?
What is the formula for using the Query Governor setting in translation = to minutes?
Sql 2000
Thanx!
-- JUDE
--=_NextPart_000_0008_01C34607.4962E840
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
My boss and I are in disagreement about the Query Governor = setting.
Can someone please tell me if the Query Governor is set to 300, how = many minutes this translates to?
What is the formula for using the Query Governor setting in = translation to minutes?
Sql 2000
Thanx!
-- JUDE
--=_NextPart_000_0008_01C34607.4962E840--This is a multi-part message in MIME format.
--=_NextPart_000_005B_01C3461B.A99E96F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Yes, that is 5 minutes. Do you have SET NOCOUNT ON in the Job or the sp =being run? What else if different between the Job and QA?
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:OfE4dFjRDHA.2148@.TK2MSFTNGP12.phx.gbl...
Andrew, Thanx for your reply.
I do remember reading this, but what I have difficulty with is the =following;
Our Query Governor is set to 300, meaning 300 seconds, which =translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it executes in =1:59.
This same stored procedure executed by way of a scheduled job returns =an error message that the Query Governor is set to 300, and this query =would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I would really =appreciate it. My boss just says "There's a bug with Query Governor", =and I don't really believe this to be the case, I think it's a case of =our not understanding well enough.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:uRZpB$iRDHA.3236@.TK2MSFTNGP10.phx.gbl...
Right from BOL:
query governor cost limit Option
Use the query governor cost limit option to specify an upper limit =for the time in which a query can run. Query cost refers to the =estimated elapsed time, in seconds, required to execute a query on a =specific hardware configuration.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:e0y2aiiRDHA.2144@.TK2MSFTNGP11.phx.gbl...
My boss and I are in disagreement about the Query Governor =setting. Can someone please tell me if the Query Governor is set to 300, =how many minutes this translates to?
What is the formula for using the Query Governor setting in =translation to minutes?
Sql 2000
Thanx!
-- JUDE
--=_NextPart_000_005B_01C3461B.A99E96F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Yes, that is 5 minutes. Do you =have SET NOCOUNT ON in the Job or the sp being run? What else if different =between the Job and QA?
-- Andrew J. KellySQL Server MVP
"JLS"
Andrew,
Thanx for your reply.
I do remember reading this, but what I have difficulty with is =the following;
Our Query Governor is set to 300, meaning 300 seconds, which =translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it =executes in 1:59.
This same stored procedure executed by way of a scheduled job =returns an error message that the Query Governor is set to 300, and this query =would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I would =really appreciate it. My boss just says "There's a bug with Query =Governor", and I don't really believe this to be the case, I think it's a case of =our not understanding well enough.
-- JUDE
"Andrew J. Kelly"
Right from BOL:
query governor =cost limit Option
Use the query governor cost limit option to specify an =upper limit for the time in which a query can run. Query cost refers to the =estimated elapsed time, in seconds, required to execute a query on a specific =hardware configuration.
-- Andrew J. KellySQL Server MVP
"JLS"
My boss and I are in disagreement about the Query Governor setting.
Can someone please tell me if the Query Governor is set to =300, how many minutes this translates to?
What is the formula for using the Query Governor setting in translation to minutes?
Sql 2000
Thanx!
-- =JUDE
--=_NextPart_000_005B_01C3461B.A99E96F0--|||This is a multi-part message in MIME format.
--=_NextPart_000_000B_01C34621.474560A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I'll have to check on the SET NOCOUNT ON, but nothing else is different =between running the proc in query analyzer and the scheduled job. Both =are done with "Exec BA_Sales_Gross_Proc"
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:eKuXx0jRDHA.3768@.tk2msftngp13.phx.gbl...
Yes, that is 5 minutes. Do you have SET NOCOUNT ON in the Job or the =sp being run? What else if different between the Job and QA?
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:OfE4dFjRDHA.2148@.TK2MSFTNGP12.phx.gbl...
Andrew, Thanx for your reply.
I do remember reading this, but what I have difficulty with is the =following;
Our Query Governor is set to 300, meaning 300 seconds, which =translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it executes in =1:59.
This same stored procedure executed by way of a scheduled job =returns an error message that the Query Governor is set to 300, and this =query would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I would really =appreciate it. My boss just says "There's a bug with Query Governor", =and I don't really believe this to be the case, I think it's a case of =our not understanding well enough.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:uRZpB$iRDHA.3236@.TK2MSFTNGP10.phx.gbl...
Right from BOL:
query governor cost limit Option
Use the query governor cost limit option to specify an upper limit =for the time in which a query can run. Query cost refers to the =estimated elapsed time, in seconds, required to execute a query on a =specific hardware configuration.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:e0y2aiiRDHA.2144@.TK2MSFTNGP11.phx.gbl...
My boss and I are in disagreement about the Query Governor =setting. Can someone please tell me if the Query Governor is set to 300, =how many minutes this translates to?
What is the formula for using the Query Governor setting in =translation to minutes?
Sql 2000
Thanx!
-- JUDE
--=_NextPart_000_000B_01C34621.474560A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I'll have to check on the SET NOCOUNT ON, but nothing else is =different between running the proc in query analyzer and the scheduled job. =Both are done with "Exec BA_Sales_Gross_Proc"
-- JUDE
"Andrew J. Kelly"
Yes, that is 5 minutes. Do you =have SET NOCOUNT ON in the Job or the sp being run? What else if =different between the Job and QA?
-- Andrew J. KellySQL Server MVP
"JLS"
Andrew,
Thanx for your reply.
I do remember reading this, but what I have difficulty with is =the following;
Our Query Governor is set to 300, meaning 300 seconds, which =translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it =executes in 1:59.
This same stored procedure executed by way of a scheduled job =returns an error message that the Query Governor is set to 300, and this =query would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I would =really appreciate it. My boss just says "There's a bug with Query =Governor", and I don't really believe this to be the case, I think it's a case =of our not understanding well enough.
-- JUDE
"Andrew J. Kelly"
Right from BOL:
query governor =cost limit Option
Use the query governor cost limit option to specify an =upper limit for the time in which a query can run. Query cost refers to =the estimated elapsed time, in seconds, required to execute a query on =a specific hardware configuration.
-- Andrew J. KellySQL Server MVP
"JLS"
My boss and I are in disagreement about the Query Governor setting.
Can someone please tell me if the Query Governor is set to =300, how many minutes this translates to?
What is the formula for using the Query Governor setting in = translation to minutes?
Sql 2000
Thanx!
-- JUDE=
--=_NextPart_000_000B_01C34621.474560A0--|||This is a multi-part message in MIME format.
--=_NextPart_000_002F_01C34621.A516B620
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
No. SET NOCOUNT ON is not present in the SP or the job. No other =differences exist between running the sp in Query Analyzer and the =scheduled job.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:eKuXx0jRDHA.3768@.tk2msftngp13.phx.gbl...
Yes, that is 5 minutes. Do you have SET NOCOUNT ON in the Job or the =sp being run? What else if different between the Job and QA?
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:OfE4dFjRDHA.2148@.TK2MSFTNGP12.phx.gbl...
Andrew, Thanx for your reply.
I do remember reading this, but what I have difficulty with is the =following;
Our Query Governor is set to 300, meaning 300 seconds, which =translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it executes in =1:59.
This same stored procedure executed by way of a scheduled job =returns an error message that the Query Governor is set to 300, and this =query would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I would really =appreciate it. My boss just says "There's a bug with Query Governor", =and I don't really believe this to be the case, I think it's a case of =our not understanding well enough.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:uRZpB$iRDHA.3236@.TK2MSFTNGP10.phx.gbl...
Right from BOL:
query governor cost limit Option
Use the query governor cost limit option to specify an upper limit =for the time in which a query can run. Query cost refers to the =estimated elapsed time, in seconds, required to execute a query on a =specific hardware configuration.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:e0y2aiiRDHA.2144@.TK2MSFTNGP11.phx.gbl...
My boss and I are in disagreement about the Query Governor =setting. Can someone please tell me if the Query Governor is set to 300, =how many minutes this translates to?
What is the formula for using the Query Governor setting in =translation to minutes?
Sql 2000
Thanx!
-- JUDE
--=_NextPart_000_002F_01C34621.A516B620
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
No. SET NOCOUNT ON is not present in the SP or the job. =No other differences exist between running the sp in Query Analyzer and the =scheduled job.
-- JUDE
"Andrew J. Kelly"
Yes, that is 5 minutes. Do you =have SET NOCOUNT ON in the Job or the sp being run? What else if =different between the Job and QA?
-- Andrew J. KellySQL Server MVP
"JLS"
Andrew,
Thanx for your reply.
I do remember reading this, but what I have difficulty with is =the following;
Our Query Governor is set to 300, meaning 300 seconds, which =translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it =executes in 1:59.
This same stored procedure executed by way of a scheduled job =returns an error message that the Query Governor is set to 300, and this =query would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I would =really appreciate it. My boss just says "There's a bug with Query =Governor", and I don't really believe this to be the case, I think it's a case =of our not understanding well enough.
-- JUDE
"Andrew J. Kelly"
Right from BOL:
query governor =cost limit Option
Use the query governor cost limit option to specify an =upper limit for the time in which a query can run. Query cost refers to =the estimated elapsed time, in seconds, required to execute a query on =a specific hardware configuration.
-- Andrew J. KellySQL Server MVP
"JLS"
My boss and I are in disagreement about the Query Governor setting.
Can someone please tell me if the Query Governor is set to =300, how many minutes this translates to?
What is the formula for using the Query Governor setting in = translation to minutes?
Sql 2000
Thanx!
-- JUDE=
--=_NextPart_000_002F_01C34621.A516B620--|||This is a multi-part message in MIME format.
--=_NextPart_000_002A_01C34623.5F211870
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Try setting it on at the beginning of the sp and see if that make a =difference. As a rule of thumb it should be included in most sp's.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:e5sf2LkRDHA.2424@.tk2msftngp13.phx.gbl...
No. SET NOCOUNT ON is not present in the SP or the job. No other =differences exist between running the sp in Query Analyzer and the =scheduled job.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:eKuXx0jRDHA.3768@.tk2msftngp13.phx.gbl...
Yes, that is 5 minutes. Do you have SET NOCOUNT ON in the Job or =the sp being run? What else if different between the Job and QA?
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:OfE4dFjRDHA.2148@.TK2MSFTNGP12.phx.gbl...
Andrew, Thanx for your reply.
I do remember reading this, but what I have difficulty with is the =following;
Our Query Governor is set to 300, meaning 300 seconds, which =translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it executes in =1:59.
This same stored procedure executed by way of a scheduled job =returns an error message that the Query Governor is set to 300, and this =query would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I would really =appreciate it. My boss just says "There's a bug with Query Governor", =and I don't really believe this to be the case, I think it's a case of =our not understanding well enough.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:uRZpB$iRDHA.3236@.TK2MSFTNGP10.phx.gbl...
Right from BOL:
query governor cost limit Option
Use the query governor cost limit option to specify an upper =limit for the time in which a query can run. Query cost refers to the =estimated elapsed time, in seconds, required to execute a query on a =specific hardware configuration.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:e0y2aiiRDHA.2144@.TK2MSFTNGP11.phx.gbl...
My boss and I are in disagreement about the Query Governor =setting. Can someone please tell me if the Query Governor is set to =300, how many minutes this translates to?
What is the formula for using the Query Governor setting in =translation to minutes?
Sql 2000
Thanx!
-- JUDE
--=_NextPart_000_002A_01C34623.5F211870
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Try setting it on at the beginning of =the sp and see if that make a difference. As a rule of thumb it should =be included in most sp's.
-- Andrew J. KellySQL Server MVP
"JLS"
No. SET NOCOUNT ON is not present in the SP or the =job. No other differences exist between running the sp in Query Analyzer and =the scheduled job.
-- JUDE
"Andrew J. Kelly"
Yes, that is 5 minutes. Do =you have SET NOCOUNT ON in the Job or the sp being run? What else if =different between the Job and QA?
-- Andrew J. KellySQL Server MVP
"JLS"
Andrew,
Thanx for your reply.
I do remember reading this, but what I have difficulty with =is the following;
Our Query Governor is set to 300, meaning 300 seconds, which translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it =executes in 1:59.
This same stored procedure executed by way of a scheduled job =returns an error message that the Query Governor is set to 300, and this =query would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I =would really appreciate it. My boss just says "There's a bug with Query Governor", and I don't really believe this to be the case, I think =it's a case of our not understanding well enough.
-- JUDE
"Andrew J. Kelly"
Right from BOL:
query governor =cost limit Option
Use the query governor cost limit option to specify an =upper limit for the time in which a query can run. Query cost refers =to the estimated elapsed time, in seconds, required to execute a query =on a specific hardware configuration.
-- Andrew J. KellySQL Server MVP
"JLS"
My boss and I are in disagreement about the Query =Governor setting.
Can someone please tell me if the Query Governor is set =to 300, how many minutes this translates to?
What is the formula for using the Query Governor setting =in translation to minutes?
Sql 2000
Thanx!
-- JUDE
--=_NextPart_000_002A_01C34623.5F211870--|||This is a multi-part message in MIME format.
--=_NextPart_000_0009_01C34631.343C8870
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Ok, I'll give it a try and thanx for this tip.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:#LNAnTkRDHA.1220@.TK2MSFTNGP12.phx.gbl...
Try setting it on at the beginning of the sp and see if that make a =difference. As a rule of thumb it should be included in most sp's.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:e5sf2LkRDHA.2424@.tk2msftngp13.phx.gbl...
No. SET NOCOUNT ON is not present in the SP or the job. No other =differences exist between running the sp in Query Analyzer and the =scheduled job.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:eKuXx0jRDHA.3768@.tk2msftngp13.phx.gbl...
Yes, that is 5 minutes. Do you have SET NOCOUNT ON in the Job or =the sp being run? What else if different between the Job and QA?
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:OfE4dFjRDHA.2148@.TK2MSFTNGP12.phx.gbl...
Andrew, Thanx for your reply.
I do remember reading this, but what I have difficulty with is =the following;
Our Query Governor is set to 300, meaning 300 seconds, which =translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it executes =in 1:59.
This same stored procedure executed by way of a scheduled job =returns an error message that the Query Governor is set to 300, and this =query would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I would really =appreciate it. My boss just says "There's a bug with Query Governor", =and I don't really believe this to be the case, I think it's a case of =our not understanding well enough.
-- JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in =message news:uRZpB$iRDHA.3236@.TK2MSFTNGP10.phx.gbl...
Right from BOL:
query governor cost limit Option
Use the query governor cost limit option to specify an upper =limit for the time in which a query can run. Query cost refers to the =estimated elapsed time, in seconds, required to execute a query on a =specific hardware configuration.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message =news:e0y2aiiRDHA.2144@.TK2MSFTNGP11.phx.gbl...
My boss and I are in disagreement about the Query Governor =setting. Can someone please tell me if the Query Governor is set to =300, how many minutes this translates to?
What is the formula for using the Query Governor setting in =translation to minutes?
Sql 2000
Thanx!
-- JUDE
--=_NextPart_000_0009_01C34631.343C8870
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'll give it a try and thanx for this tip.
-- JUDE
"Andrew J. Kelly"
Try setting it on at the beginning of =the sp and see if that make a difference. As a rule of thumb it =should be included in most sp's.
-- Andrew J. KellySQL Server MVP
"JLS"
No. SET NOCOUNT ON is not present in the SP or the =job. No other differences exist between running the sp in Query Analyzer and =the scheduled job.
-- JUDE
"Andrew J. Kelly"
Yes, that is 5 minutes. Do =you have SET NOCOUNT ON in the Job or the sp being run? What else if =different between the Job and QA?
-- Andrew J. KellySQL Server MVP
"JLS"
Andrew,
Thanx for your reply.
I do remember reading this, but what I have difficulty with =is the following;
Our Query Governor is set to 300, meaning 300 seconds, =which translates to 5 minutes, right?
When I execute a stored procedure in Query Analyzer it = executes in 1:59.
This same stored procedure executed by way of a scheduled =job returns an error message that the Query Governor is set to 300, =and this query would need 437 to execute, therefore, fails.
Can you shed any light on this situation for me? I =would really appreciate it. My boss just says "There's a bug =with Query Governor", and I don't really believe this to be the case, I =think it's a case of our not understanding well enough.
-- JUDE
"Andrew J. Kelly"
Right from BOL:
query =governor cost limit Option
Use the query governor cost limit option to specify =an upper limit for the time in which a query can run. Query cost refers =to the estimated elapsed time, in seconds, required to execute a =query on a specific hardware configuration.
-- Andrew J. KellySQL Server MVP
"JLS"
My boss and I are in disagreement about the Query =Governor setting.
Can someone please tell me if the Query Governor is set =to 300, how many minutes this translates to?
What is the formula for using the Query Governor =setting in translation to minutes?
Sql 2000
Thanx!
-- =JUDE
--=_NextPart_000_0009_01C34631.343C8870--|||Also, you could try running a profiler trace while executing the proc from QA and Agent and
compare the plans. Other SET options can affect the plan that the optimizer is deciding on.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"JLS" <judy.shoop@.sartomer.com> wrote in message news:uFLnFKlRDHA.2116@.TK2MSFTNGP12.phx.gbl...
Ok, I'll give it a try and thanx for this tip.
--
JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:#LNAnTkRDHA.1220@.TK2MSFTNGP12.phx.gbl...
Try setting it on at the beginning of the sp and see if that make a difference. As a rule of
thumb it should be included in most sp's.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message
news:e5sf2LkRDHA.2424@.tk2msftngp13.phx.gbl...
No. SET NOCOUNT ON is not present in the SP or the job. No other differences exist between
running the sp in Query Analyzer and the scheduled job.
--
JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eKuXx0jRDHA.3768@.tk2msftngp13.phx.gbl...
Yes, that is 5 minutes. Do you have SET NOCOUNT ON in the Job or the sp being run? What
else if different between the Job and QA?
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message
news:OfE4dFjRDHA.2148@.TK2MSFTNGP12.phx.gbl...
Andrew,
Thanx for your reply.
I do remember reading this, but what I have difficulty with is the following;
Our Query Governor is set to 300, meaning 300 seconds, which translates to 5 minutes,
right?
When I execute a stored procedure in Query Analyzer it executes in 1:59.
This same stored procedure executed by way of a scheduled job returns an error message
that the Query Governor is set to 300, and this query would need 437 to execute, therefore,
fails.
Can you shed any light on this situation for me? I would really appreciate it. My boss
just says "There's a bug with Query Governor", and I don't really believe this to be the case, I
think it's a case of our not understanding well enough.
--
JUDE
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uRZpB$iRDHA.3236@.TK2MSFTNGP10.phx.gbl...
Right from BOL:
query governor cost limit Option
Use the query governor cost limit option to specify an upper limit for the time in
which a query can run. Query cost refers to the estimated elapsed time, in seconds, required to
execute a query on a specific hardware configuration.
--
Andrew J. Kelly
SQL Server MVP
"JLS" <judy.shoop@.sartomer.com> wrote in message
news:e0y2aiiRDHA.2144@.TK2MSFTNGP11.phx.gbl...
My boss and I are in disagreement about the Query Governor setting.
Can someone please tell me if the Query Governor is set to 300, how many minutes
this translates to?
What is the formula for using the Query Governor setting in translation to minutes?
Sql 2000
Thanx!
--
JUDE
No comments:
Post a Comment