Bug in SP4

Hi,
I met a bug in SP4. I did the same test on two machines. One is a windows
2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 2000
develope SP3. Both machines can't run any jobs by sp_start_job stored
procedure after installation of SP4. Same to sp_stop_job. The error is:
Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 61
The specified @.job_name ('test1') does not exist.
Both stored procedures run well in SP3, but not in SP4. I am sure it's a bug
in SP4.
Bill
Bill,
I just tested this on w2000, SP4, and was able to start a job. Is it maybe
that you were using a non-sysadmin login, so didn't have access to the
msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view and
then from sysjobs to see.
"Bill Wang" wrote:

> Hi,
> I met a bug in SP4. I did the same test on two machines. One is a windows
> 2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 2000
> develope SP3. Both machines can't run any jobs by sp_start_job stored
> procedure after installation of SP4. Same to sp_stop_job. The error is:
> Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 61
> The specified @.job_name ('test1') does not exist.
> Both stored procedures run well in SP3, but not in SP4. I am sure it's a bug
> in SP4.
> Bill
|||Thanks, Mary.
I tested the select from sysjobs and sysjobs_view. No permission issues on
these two table/view. Itested SP4 with sa. Before installation of SP4, I can
run these stored procedure, then install SP4 and run it with same user. It
failed with the error.
Did you install other hotfix after SP4 ?
Thanks!
Bill
"Mary" wrote:
[vbcol=seagreen]
> Bill,
> I just tested this on w2000, SP4, and was able to start a job. Is it maybe
> that you were using a non-sysadmin login, so didn't have access to the
> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view and
> then from sysjobs to see.
> "Bill Wang" wrote:
|||Sorry, if you create a new job after SP4, it's OK. But you can't run any jobs
by sp_start_job on old jobs created on SP3.
Bill
"Mary" wrote:
[vbcol=seagreen]
> Bill,
> I just tested this on w2000, SP4, and was able to start a job. Is it maybe
> that you were using a non-sysadmin login, so didn't have access to the
> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view and
> then from sysjobs to see.
> "Bill Wang" wrote:
|||I tried this using Dev Edition on XP and didn't see this behaviour. After
upgrading from SP3 to SP4 calls to sp_start_job either from another job or
Query Analyzer ran fine (all jobs owned by sa). What collation is your
sevrer and are your jobs owned by sa or another user? Are you calling
sp_start_job when logged in as a sysadmin?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:13316834-4E2C-4AF2-B838-1CD16C106C7B@.microsoft.com...[vbcol=seagreen]
> Sorry, if you create a new job after SP4, it's OK. But you can't run any
> jobs
> by sp_start_job on old jobs created on SP3.
> Bill
> "Mary" wrote:

Bug in SP4

Hi,
I met a bug in SP4. I did the same test on two machines. One is a windows
2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 2000
develope SP3. Both machines can't run any jobs by sp_start_job stored
procedure after installation of SP4. Same to sp_stop_job. The error is:
Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 61
The specified @.job_name ('test1') does not exist.
Both stored procedures run well in SP3, but not in SP4. I am sure it's a bug
in SP4.
BillBill,
I just tested this on w2000, SP4, and was able to start a job. Is it maybe
that you were using a non-sysadmin login, so didn't have access to the
msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view and
then from sysjobs to see.
"Bill Wang" wrote:
> Hi,
> I met a bug in SP4. I did the same test on two machines. One is a windows
> 2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 2000
> develope SP3. Both machines can't run any jobs by sp_start_job stored
> procedure after installation of SP4. Same to sp_stop_job. The error is:
> Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 61
> The specified @.job_name ('test1') does not exist.
> Both stored procedures run well in SP3, but not in SP4. I am sure it's a bug
> in SP4.
> Bill|||Thanks, Mary.
I tested the select from sysjobs and sysjobs_view. No permission issues on
these two table/view. Itested SP4 with sa. Before installation of SP4, I can
run these stored procedure, then install SP4 and run it with same user. It
failed with the error.
Did you install other hotfix after SP4 ?
Thanks!
Bill
"Mary" wrote:
> Bill,
> I just tested this on w2000, SP4, and was able to start a job. Is it maybe
> that you were using a non-sysadmin login, so didn't have access to the
> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view and
> then from sysjobs to see.
> "Bill Wang" wrote:
> > Hi,
> > I met a bug in SP4. I did the same test on two machines. One is a windows
> > 2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 2000
> > develope SP3. Both machines can't run any jobs by sp_start_job stored
> > procedure after installation of SP4. Same to sp_stop_job. The error is:
> >
> > Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> > Line 61
> > The specified @.job_name ('test1') does not exist.
> >
> > Both stored procedures run well in SP3, but not in SP4. I am sure it's a bug
> > in SP4.
> >
> > Bill|||Sorry, if you create a new job after SP4, it's OK. But you can't run any jobs
by sp_start_job on old jobs created on SP3.
Bill
"Mary" wrote:
> Bill,
> I just tested this on w2000, SP4, and was able to start a job. Is it maybe
> that you were using a non-sysadmin login, so didn't have access to the
> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view and
> then from sysjobs to see.
> "Bill Wang" wrote:
> > Hi,
> > I met a bug in SP4. I did the same test on two machines. One is a windows
> > 2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 2000
> > develope SP3. Both machines can't run any jobs by sp_start_job stored
> > procedure after installation of SP4. Same to sp_stop_job. The error is:
> >
> > Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> > Line 61
> > The specified @.job_name ('test1') does not exist.
> >
> > Both stored procedures run well in SP3, but not in SP4. I am sure it's a bug
> > in SP4.
> >
> > Bill|||I tried this using Dev Edition on XP and didn't see this behaviour. After
upgrading from SP3 to SP4 calls to sp_start_job either from another job or
Query Analyzer ran fine (all jobs owned by sa). What collation is your
sevrer and are your jobs owned by sa or another user? Are you calling
sp_start_job when logged in as a sysadmin?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:13316834-4E2C-4AF2-B838-1CD16C106C7B@.microsoft.com...
> Sorry, if you create a new job after SP4, it's OK. But you can't run any
> jobs
> by sp_start_job on old jobs created on SP3.
> Bill
> "Mary" wrote:
>> Bill,
>> I just tested this on w2000, SP4, and was able to start a job. Is it
>> maybe
>> that you were using a non-sysadmin login, so didn't have access to the
>> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view
>> and
>> then from sysjobs to see.
>> "Bill Wang" wrote:
>> > Hi,
>> > I met a bug in SP4. I did the same test on two machines. One is a
>> > windows
>> > 2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL
>> > Server 2000
>> > develope SP3. Both machines can't run any jobs by sp_start_job stored
>> > procedure after installation of SP4. Same to sp_stop_job. The error is:
>> >
>> > Server: Msg 14262, Level 16, State 1, Procedure
>> > sp_verify_job_identifiers,
>> > Line 61
>> > The specified @.job_name ('test1') does not exist.
>> >
>> > Both stored procedures run well in SP3, but not in SP4. I am sure it's
>> > a bug
>> > in SP4.
>> >
>> > Bill

Bug in SP4

Hi,
I met a bug in SP4. I did the same test on two machines. One is a windows
2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 200
0
develope SP3. Both machines can't run any jobs by sp_start_job stored
procedure after installation of SP4. Same to sp_stop_job. The error is:
Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 61
The specified @.job_name ('test1') does not exist.
Both stored procedures run well in SP3, but not in SP4. I am sure it's a bug
in SP4.
BillBill,
I just tested this on w2000, SP4, and was able to start a job. Is it maybe
that you were using a non-sysadmin login, so didn't have access to the
msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view and
then from sysjobs to see.
"Bill Wang" wrote:

> Hi,
> I met a bug in SP4. I did the same test on two machines. One is a windo
ws
> 2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 2
000
> develope SP3. Both machines can't run any jobs by sp_start_job stored
> procedure after installation of SP4. Same to sp_stop_job. The error is:
> Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 61
> The specified @.job_name ('test1') does not exist.
> Both stored procedures run well in SP3, but not in SP4. I am sure it's a b
ug
> in SP4.
> Bill|||Thanks, Mary.
I tested the select from sysjobs and sysjobs_view. No permission issues on
these two table/view. Itested SP4 with sa. Before installation of SP4, I can
run these stored procedure, then install SP4 and run it with same user. It
failed with the error.
Did you install other hotfix after SP4 ?
Thanks!
Bill
"Mary" wrote:
[vbcol=seagreen]
> Bill,
> I just tested this on w2000, SP4, and was able to start a job. Is it mayb
e
> that you were using a non-sysadmin login, so didn't have access to the
> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view an
d
> then from sysjobs to see.
> "Bill Wang" wrote:
>|||Sorry, if you create a new job after SP4, it's OK. But you can't run any job
s
by sp_start_job on old jobs created on SP3.
Bill
"Mary" wrote:
[vbcol=seagreen]
> Bill,
> I just tested this on w2000, SP4, and was able to start a job. Is it mayb
e
> that you were using a non-sysadmin login, so didn't have access to the
> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view an
d
> then from sysjobs to see.
> "Bill Wang" wrote:
>|||I tried this using Dev Edition on XP and didn't see this behaviour. After
upgrading from SP3 to SP4 calls to sp_start_job either from another job or
Query Analyzer ran fine (all jobs owned by sa). What collation is your
sevrer and are your jobs owned by sa or another user? Are you calling
sp_start_job when logged in as a sysadmin?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:13316834-4E2C-4AF2-B838-1CD16C106C7B@.microsoft.com...[vbcol=seagreen]
> Sorry, if you create a new job after SP4, it's OK. But you can't run any
> jobs
> by sp_start_job on old jobs created on SP3.
> Bill
> "Mary" wrote:
>

bug described in article 872843

I am experiencing same problem described in article 872843. even though my
sql server is on SP4.
I try to tweak Log reader Agent Properties & other things but that is not
helping.
It is my impression whether this bug is not fixed or got break in SP4.
Any reply/feedback/solutions/tips will be highly appreciated.
Can you try to reapply the SP. There have been instances where the sp was
not completely applied.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jay" <sqldba@.abc.com> wrote in message
news:7f4e272a5b544937af6958bf9119db34@.ureader.com. ..
>I am experiencing same problem described in article 872843. even though my
> sql server is on SP4.
> I try to tweak Log reader Agent Properties & other things but that is not
> helping.
> It is my impression whether this bug is not fixed or got break in SP4.
> Any reply/feedback/solutions/tips will be highly appreciated.

Buffer Overrun reported in SQLDiag

I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
(Active/ Passive), and have started to get Buffer Overrun errors on running
SQLDiag - as follows :
/********************************
Event ID:26
User:N/A
Description:
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
/********************************
SQLDiag is being run by an SQL job running an OS command as follows :
SQLDiag -O Z:\Outputsqldiag.txt -E -C
This was always successful prior to the installation of SP4. There seems to
be nothing about this on the web...
Any thoughts or comments gratefully received.
This is a known bug... I don't think there is anything you can do about it
until it is fixed, but it has been reported...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"BarryC" <BarryC@.discussions.microsoft.com> wrote in message
news:45D5EBF1-0642-46D9-A3A0-696FBC1C2650@.microsoft.com...
>I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on
> running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
> to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.
|||SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
around for an immediate solution
Rename the existing SQLDiag.exe (SP4)
Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
the Binn folder
This old version SQLDiag works fine with the SP4. I tested this solution
and it works fine.
"BarryC" wrote:

> I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on running
> SQLDiag - as follows :
> /********************************
> Event ID:26
> User:N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.
|||Thanks for that - in testing at the moment, but its looking good. Have MS
got an official line on this one yet?
"M. S. Reddy" wrote:
[vbcol=seagreen]
> SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
> around for an immediate solution
> Rename the existing SQLDiag.exe (SP4)
> Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
> the Binn folder
> This old version SQLDiag works fine with the SP4. I tested this solution
> and it works fine.
>
>
>
> "BarryC" wrote:

Buffer Overrun reported in SQLDiag

I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
(Active/ Passive), and have started to get Buffer Overrun errors on running
SQLDiag - as follows :
/********************************
Event ID: 26
User: N/A
Description:
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
/********************************
SQLDiag is being run by an SQL job running an OS command as follows :
SQLDiag -O Z:\Outputsqldiag.txt -E -C
This was always successful prior to the installation of SP4. There seems to
be nothing about this on the web...
Any thoughts or comments gratefully received.This is a known bug... I don't think there is anything you can do about it
until it is fixed, but it has been reported...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"BarryC" <BarryC@.discussions.microsoft.com> wrote in message
news:45D5EBF1-0642-46D9-A3A0-696FBC1C2650@.microsoft.com...
>I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on
> running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
> to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
around for an immediate solution
Rename the existing SQLDiag.exe (SP4)
Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
the Binn folder
This old version SQLDiag works fine with the SP4. I tested this solution
and it works fine.
"BarryC" wrote:
> I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||Thanks for that - in testing at the moment, but its looking good. Have MS
got an official line on this one yet?
"M. S. Reddy" wrote:
> SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
> around for an immediate solution
> Rename the existing SQLDiag.exe (SP4)
> Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
> the Binn folder
> This old version SQLDiag works fine with the SP4. I tested this solution
> and it works fine.
>
>
>
> "BarryC" wrote:
> > I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> > (Active/ Passive), and have started to get Buffer Overrun errors on running
> > SQLDiag - as follows :
> >
> > /********************************
> > Event ID: 26
> > User: N/A
> > Description:
> > Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> > detected!
> >
> > Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> >
> > A buffer overrun has been detected which has corrupted the program's
> > internal state. The program cannot safely continue execution and must
> > now be terminated.
> > /********************************
> >
> > SQLDiag is being run by an SQL job running an OS command as follows :
> >
> > SQLDiag -O Z:\Outputsqldiag.txt -E -C
> >
> > This was always successful prior to the installation of SP4. There seems to
> > be nothing about this on the web...
> >
> > Any thoughts or comments gratefully received.

Buffer Overrun reported in SQLDiag

I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
(Active/ Passive), and have started to get Buffer Overrun errors on running
SQLDiag - as follows :
/********************************
Event ID: 26
User: N/A
Description:
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
/********************************
SQLDiag is being run by an SQL job running an OS command as follows :
SQLDiag -O Z:\Outputsqldiag.txt -E -C
This was always successful prior to the installation of SP4. There seems to
be nothing about this on the web...
Any thoughts or comments gratefully received.This is a known bug... I don't think there is anything you can do about it
until it is fixed, but it has been reported...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"BarryC" <BarryC@.discussions.microsoft.com> wrote in message
news:45D5EBF1-0642-46D9-A3A0-696FBC1C2650@.microsoft.com...
>I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on
> running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
> to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
around for an immediate solution
Rename the existing SQLDiag.exe (SP4)
Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
the Binn folder
This old version SQLDiag works fine with the SP4. I tested this solution
and it works fine.
"BarryC" wrote:

> I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on runnin
g
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||Thanks for that - in testing at the moment, but its looking good. Have MS
got an official line on this one yet?
"M. S. Reddy" wrote:
[vbcol=seagreen]
> SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this wo
rk
> around for an immediate solution
> Rename the existing SQLDiag.exe (SP4)
> Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0)
to
> the Binn folder
> This old version SQLDiag works fine with the SP4. I tested this solution
> and it works fine.
>
>
>
> "BarryC" wrote:
>

Buffer overrun detected

When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
Cluster (Active/Active), I receive the next message:
Buffer Overrun detected!
A buffer overrun has been detected which has corrupted the programs internal
state. The program cannot safely continue execution and must now be
terminated.
In a cluster I have two instances. The first instance installed perfect but
in second instance have a problem describe above.
Thank youHi, we've just come across this too. Has anyone got a solution?
BruceB
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1757341.html|||Hi
You may want to call PSS on this one.
John
"Mario Felix Filho" <Mario Felix Filho@.discussions.microsoft.com> wrote in
message news:DA97BB4C-309E-4CDF-A1F2-A2B4851D264F@.microsoft.com...
> When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
> Cluster (Active/Active), I receive the next message:
> Buffer Overrun detected!
> A buffer overrun has been detected which has corrupted the programs
> internal
> state. The program cannot safely continue execution and must now be
> terminated.
> In a cluster I have two instances. The first instance installed perfect
> but
> in second instance have a problem describe above.
> Thank you
>

Buffer overrun detected

When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
Cluster (Active/Active), I receive the next message:
Buffer Overrun detected!
A buffer overrun has been detected which has corrupted the programs internal
state. The program cannot safely continue execution and must now be
terminated.
In a cluster I have two instances. The first instance installed perfect but
in second instance have a problem describe above.
Thank you
Hi, we've just come across this too. Has anyone got a solution?|||Hi
You may want to call PSS on this one.
John
"Mario Felix Filho" <Mario Felix Filho@.discussions.microsoft.com> wrote in
message news:DA97BB4C-309E-4CDF-A1F2-A2B4851D264F@.microsoft.com...
> When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
> Cluster (Active/Active), I receive the next message:
> Buffer Overrun detected!
> A buffer overrun has been detected which has corrupted the programs
> internal
> state. The program cannot safely continue execution and must now be
> terminated.
> In a cluster I have two instances. The first instance installed perfect
> but
> in second instance have a problem describe above.
> Thank you
>

Buffer overrun detected

When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
Cluster (Active/Active), I receive the next message:
Buffer Overrun detected!
A buffer overrun has been detected which has corrupted the programs internal
state. The program cannot safely continue execution and must now be
terminated.
In a cluster I have two instances. The first instance installed perfect but
in second instance have a problem describe above.
Thank youHi
You may want to call PSS on this one.
John
"Mario Felix Filho" <Mario Felix Filho@.discussions.microsoft.com> wrote in
message news:DA97BB4C-309E-4CDF-A1F2-A2B4851D264F@.microsoft.com...
> When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
> Cluster (Active/Active), I receive the next message:
> Buffer Overrun detected!
> A buffer overrun has been detected which has corrupted the programs
> internal
> state. The program cannot safely continue execution and must now be
> terminated.
> In a cluster I have two instances. The first instance installed perfect
> but
> in second instance have a problem describe above.
> Thank you
>

buffer cache hit ratio estimation

Hi
I have trouble with MSSQL2000 SP4 (without any hotfixes). During last two
weeks it start works anormally. After last optimalization (about few months
ago) it works good (fast, without blocks). Its buffer cache hit ratio was
about 99.7-99.8. Last day it starts work slow, there was many blocks and
dedlocks. There are no any queries, jobs and applications was added. Now
buffer cache hit ratio oscilate about 95-98. I try update statistics and
reindex some hard used tables, but there is no effect or effect is wery
short (after few hours problem return).
Mayby somene know what it could be?
Is it possible to estimate how each table (using DBCC SHOW_STATISTICS or
DBCC SHOWCONTIG or others) how the table affect on total buffer cache hit
ratio?
Marek
--
www.programowanieobiektowe.plChances are you are now scanning a table(s) where as before you were doing
seeks. You need to profile the queries to see which are the poorly
performing ones (ones with high duration and reads) and address why.
Andrew J. Kelly SQL MVP
"Marek Wierzbicki" <marek.wierzbickiiiii@.azymuttttt.pl> wrote in message
news:ed8rmq$1h4p$1@.news2.ipartners.pl...
> Hi
> I have trouble with MSSQL2000 SP4 (without any hotfixes). During last two
> weeks it start works anormally. After last optimalization (about few
> months ago) it works good (fast, without blocks). Its buffer cache hit
> ratio was about 99.7-99.8. Last day it starts work slow, there was many
> blocks and dedlocks. There are no any queries, jobs and applications was
> added. Now buffer cache hit ratio oscilate about 95-98. I try update
> statistics and reindex some hard used tables, but there is no effect or
> effect is wery short (after few hours problem return).
> Mayby somene know what it could be?
> Is it possible to estimate how each table (using DBCC SHOW_STATISTICS or
> DBCC SHOWCONTIG or others) how the table affect on total buffer cache hit
> ratio?
> Marek
> --
> www.programowanieobiektowe.pl|||> Chances are you are now scanning a table(s) where as before you were doing
> seeks. You need to profile the queries to see which are the poorly
> performing ones (ones with high duration and reads) and address why.
profiler didn't show any long time and expansive queries, but some simple
queries work about minute (not secounds like earlier)
Marek|||Then you need to find out why. Are there high disk queues? High CPU? Is
there blocking for those queries? You have to narrow it down so you can
start addressing the real issue. Maybe these will help:
http://www.sql-server-performance.com/sql_server_performance_audit10.asp
Performance Audit
http://www.microsoft.com/technet/prodtechnol/sql/2005/library/operations.mspx
Performance WP's
http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
http://www.sql-server-performance.com/sql_server_performance_audit.asp
Hardware Performance CheckList
http://www.sql-server-performance.com/best_sql_server_performance_tips.asp
SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=224587 Troubleshooting App
Performance
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_24u1.asp
Disk Monitoring
http://sqldev.net/misc/WaitTypes.htm Wait Types
Tempdb in 2005:
http://download.microsoft.com/download/4/f/8/4f8f2dc9-a9a7-4b68-98cb-163482c95e0b/WorkingWithTempDB.doc
Physical Database Storage:
http://download.microsoft.com/download/4/f/8/4f8f2dc9-a9a7-4b68-98cb-163482c95e0b/PhysDBStor.doc
--
Andrew J. Kelly SQL MVP
"Marek Wierzbicki" <marek.wierzbickiiiii@.azymuttttt.pl> wrote in message
news:edh8j6$4jj$1@.news2.ipartners.pl...
>> Chances are you are now scanning a table(s) where as before you were
>> doing seeks. You need to profile the queries to see which are the poorly
>> performing ones (ones with high duration and reads) and address why.
> profiler didn't show any long time and expansive queries, but some simple
> queries work about minute (not secounds like earlier)
>
> Marek
>|||> Then you need to find out why. Are there high disk queues? High CPU? Is
> there blocking for those queries? You have to narrow it down so you can
> start addressing the real issue. Maybe these will help:
I will try Your links. during hi trouble periods disk quees is over 50-60
Marek

buffer cache hit ratio estimation

Hi
I have trouble with MSSQL2000 SP4 (without any hotfixes). During last two
weeks it start works anormally. After last optimalization (about few months
ago) it works good (fast, without blocks). Its buffer cache hit ratio was
about 99.7-99.8. Last day it starts work slow, there was many blocks and
dedlocks. There are no any queries, jobs and applications was added. Now
buffer cache hit ratio oscilate about 95-98. I try update statistics and
reindex some hard used tables, but there is no effect or effect is wery
short (after few hours problem return).
Mayby somene know what it could be?
Is it possible to estimate how each table (using DBCC SHOW_STATISTICS or
DBCC SHOWCONTIG or others) how the table affect on total buffer cache hit
ratio?
Marek
www.programowanieobiektowe.plChances are you are now scanning a table(s) where as before you were doing
seeks. You need to profile the queries to see which are the poorly
performing ones (ones with high duration and reads) and address why.
Andrew J. Kelly SQL MVP
"Marek Wierzbicki" <marek.wierzbickiiiii@.azymuttttt.pl> wrote in message
news:ed8rmq$1h4p$1@.news2.ipartners.pl...
> Hi
> I have trouble with MSSQL2000 SP4 (without any hotfixes). During last two
> weeks it start works anormally. After last optimalization (about few
> months ago) it works good (fast, without blocks). Its buffer cache hit
> ratio was about 99.7-99.8. Last day it starts work slow, there was many
> blocks and dedlocks. There are no any queries, jobs and applications was
> added. Now buffer cache hit ratio oscilate about 95-98. I try update
> statistics and reindex some hard used tables, but there is no effect or
> effect is wery short (after few hours problem return).
> Mayby somene know what it could be?
> Is it possible to estimate how each table (using DBCC SHOW_STATISTICS or
> DBCC SHOWCONTIG or others) how the table affect on total buffer cache hit
> ratio?
> Marek
> --
> www.programowanieobiektowe.pl|||> Chances are you are now scanning a table(s) where as before you were doing
> seeks. You need to profile the queries to see which are the poorly
> performing ones (ones with high duration and reads) and address why.
profiler didn't show any long time and expansive queries, but some simple
queries work about minute (not secounds like earlier)
Marek|||Then you need to find out why. Are there high disk queues? High CPU? Is
there blocking for those queries? You have to narrow it down so you can
start addressing the real issue. Maybe these will help:
http://www.sql-server-performance.c...nce_audit10.asp
Performance Audit
http://www.microsoft.com/technet/pr...perfmonitor.asp Perfmon counters
http://www.sql-server-performance.c...mance_audit.asp
Hardware Performance CheckList
http://www.sql-server-performance.c...rmance_tips.asp
SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=224587 Troubleshooting App
Performance
http://msdn.microsoft.com/library/d.../>
on_24u1.asp
Disk Monitoring
http://sqldev.net/misc/WaitTypes.htm Wait Types
Tempdb in 2005:
http://download.microsoft.com/downl...gWithTempDB.doc
Physical Database Storage:
http://download.microsoft.com/downl...
PhysDBStor.doc
Andrew J. Kelly SQL MVP
"Marek Wierzbicki" <marek.wierzbickiiiii@.azymuttttt.pl> wrote in message
news:edh8j6$4jj$1@.news2.ipartners.pl...
> profiler didn't show any long time and expansive queries, but some simple
> queries work about minute (not secounds like earlier)
>
> Marek
>|||> Then you need to find out why. Are there high disk queues? High CPU? Is
> there blocking for those queries? You have to narrow it down so you can
> start addressing the real issue. Maybe these will help:
I will try Your links. during hi trouble periods disk quees is over 50-60
Marek

Broken Linked Server

Been running SQL 7.0 sp4 for 1 1/2 years on two NT4.0 sp6a
servers on the same subnet with no problems. ServerA is
linked to ServerB, and ServerB is linked to ServerA.
I haven't loaded any new software. This past Monday, all
the jobs on ServerA that use data from ServerB failed.
All the jobs on ServerB that use data on ServerA failed.
I have not been able to figure out what caused the
problem, nor have I been able to correct the problem. I
deleted the link on each server, and tried recreating the
link but failed with the errorlog showing "Login failed
for user "ServerA(B)\Administrator". Same error on both
machines. Yet, both servers are able to successfully
register with each other through EM. The audit log shows
the message "Login succeeded for user 'ServerA(B)
\Administrator'.connection:Trusted." So, I would assume,
that they can communicate with each other.
I even deleted all my network services/protocols then
reinstalled them with no help.
Any ideas?
Did the passwords change on the Administrator account?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Nope. Nobody else admins the account. I thought the same thing, and
just in
case recent them. It didn't help. What I don't get is the server,
through EM,
can successfully register both servers (which uses the account I logged
in with),
but can't link the servers (which I map to the very same account).
Kevin McDonnell [MSFT] wrote:

>Did the passwords change on the Administrator account?
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>
>

bpasetup install interruption?

Hi- My basic bpasetup install is not completing on Win2000 Advanced Server SP4/SQL Server 2000.
I get to the point where I enter my servername and authentication mode. I have tried my server name and my servername\instance name in both security modes. Nothing seems to compete the installation (the message says it is interrupted and to restart the
install).
How can I get it to complete? I have disabled McAffee as well but left up all SQL services.
Thanks!
Susan
Can you please generate an installation log and post it here or send it to
me?
To generate the verbose log run:
msiexec.exe /i BPASETUP.msi /L*v .\bpainstall.log
- Christian
___________________________
Christian Kleinerman
Program Manager, SQL Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Susan" <Susan@.discussions.microsoft.com> wrote in message
news:8C94F4F9-05A7-48E6-8296-FEC352D17EF3@.microsoft.com...
> Hi- My basic bpasetup install is not completing on Win2000 Advanced Server
SP4/SQL Server 2000.
> I get to the point where I enter my servername and authentication mode. I
have tried my server name and my servername\instance name in both security
modes. Nothing seems to compete the installation (the message says it is
interrupted and to restart the install).
> How can I get it to complete? I have disabled McAffee as well but left up
all SQL services.
> Thanks!
|||Christian- I emailed you the log but the post here has a limit of 30000 text (the log isdouble). Please email me if you haven't received or a preferred area where I can post/ftp the log to you. Thanks- Susan
Thanks!

Both Versions of .NET & Reporting Services

I have a windows 2000 SP4 server on which I have installed Reporting Services
but keep getting a "Access Denied 401" error.
Could this be because I am running both versions of .NET
.net 1.0 SP1
.net 1.1
?
--
EdgarNot as long as ASP.NET is using the latest version (1.1). You might try
aspnet_regiis -i in the 1.1 directory.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"mresanchez" <mresanchez@.donot-spam.com> wrote in message
news:769E4D70-3104-4D12-AE5C-690664353C7C@.microsoft.com...
>I have a windows 2000 SP4 server on which I have installed Reporting
>Services
> but keep getting a "Access Denied 401" error.
> Could this be because I am running both versions of .NET
> .net 1.0 SP1
> .net 1.1
> ?
> --
> Edgar|||Brian,
When I installed RS, the setup automatically put it in the "Default" Web
Site. I have since moved it to a different Web Site & Copied all the
permissions, etc. Does RS have to be on its on dedicated Web Site (Ip
Address) or can it simply be made part of a different web site as a new
Virtual Directory (mysite.com/Reports)?
"Brian Welcker [MS]" wrote:
> Not as long as ASP.NET is using the latest version (1.1). You might try
> aspnet_regiis -i in the 1.1 directory.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "mresanchez" <mresanchez@.donot-spam.com> wrote in message
> news:769E4D70-3104-4D12-AE5C-690664353C7C@.microsoft.com...
> >I have a windows 2000 SP4 server on which I have installed Reporting
> >Services
> > but keep getting a "Access Denied 401" error.
> >
> > Could this be because I am running both versions of .NET
> > .net 1.0 SP1
> > .net 1.1
> > ?
> > --
> > Edgar
>
>|||It can be in any web site. However, unless you are running Windows Server
2003, all application within a web site share the same version of the
frameworks (since there is only one worker process). On Windows Server 2003,
you can create multiple application pools with different versions of the
Frameworks and then assign applications to them.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"mresanchez" <mresanchez@.donot-spam.com> wrote in message
news:6620EDB4-04EB-4A1E-83DD-28153B2F02DB@.microsoft.com...
> Brian,
> When I installed RS, the setup automatically put it in the "Default" Web
> Site. I have since moved it to a different Web Site & Copied all the
> permissions, etc. Does RS have to be on its on dedicated Web Site (Ip
> Address) or can it simply be made part of a different web site as a new
> Virtual Directory (mysite.com/Reports)?
> "Brian Welcker [MS]" wrote:
>> Not as long as ASP.NET is using the latest version (1.1). You might try
>> aspnet_regiis -i in the 1.1 directory.
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "mresanchez" <mresanchez@.donot-spam.com> wrote in message
>> news:769E4D70-3104-4D12-AE5C-690664353C7C@.microsoft.com...
>> >I have a windows 2000 SP4 server on which I have installed Reporting
>> >Services
>> > but keep getting a "Access Denied 401" error.
>> >
>> > Could this be because I am running both versions of .NET
>> > .net 1.0 SP1
>> > .net 1.1
>> > ?
>> > --
>> > Edgar
>>

Boost SQL Priority Pros and Cons

hello,
I have a single, dual-processor SQL server running our companies primary
application for 60 users. We are running SQL 2000 sp4 on 2000 Server, sp4.
Server access via the application seems sluggish at times and I am wondering
if boosting the SQL Priority will help in this regard.
Can someone provide some details on the pro's and con's of enabling this?
Also, what benefit would adding the instance of SQL to Active Directory
provide?
--
Thanks, Jeff"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:3E28C261-C90B-4BA1-AD6A-898AEE7B09BF@.microsoft.com...
> hello,
> I have a single, dual-processor SQL server running our companies primary
> application for 60 users. We are running SQL 2000 sp4 on 2000 Server,
> sp4.
> Server access via the application seems sluggish at times and I am
> wondering
> if boosting the SQL Priority will help in this regard.
> Can someone provide some details on the pro's and con's of enabling this?
>
If there are no other applciations running on the server, booting priority
will do nothing. If there are other application running on the server using
lots of CPU, consider using Windows Server Resource Manager to allocate CPU.
It's much more flexible, smarter and safer than messing with process
priority. T
> Also, what benefit would adding the instance of SQL to Active Directory
> provide?
>
None.
David|||If you have performance problems, looking at changing
configuration settings is generally one of the last things
you would typically look at. Many of the times that people
change those settings, it just causes more harm than good.
It's pretty rare to ever need to change the priority.
The following is a pretty good short article on the
configuration settings:
How to determine proper SQL Server configuration settings
http://support.microsoft.com/?id=319942
-Sue
On Thu, 27 Jul 2006 15:04:01 -0700, Jeff
<Jeff@.discussions.microsoft.com> wrote:
>hello,
>I have a single, dual-processor SQL server running our companies primary
>application for 60 users. We are running SQL 2000 sp4 on 2000 Server, sp4.
>Server access via the application seems sluggish at times and I am wondering
>if boosting the SQL Priority will help in this regard.
>Can someone provide some details on the pro's and con's of enabling this?
>Also, what benefit would adding the instance of SQL to Active Directory
>provide?|||Jeff wrote:
> hello,
> I have a single, dual-processor SQL server running our companies primary
> application for 60 users. We are running SQL 2000 sp4 on 2000 Server, sp4.
> Server access via the application seems sluggish at times and I am wondering
> if boosting the SQL Priority will help in this regard.
> Can someone provide some details on the pro's and con's of enabling this?
> Also, what benefit would adding the instance of SQL to Active Directory
> provide?
>
More than likely, boosting the priority won't help you out at all. You
should start by looking at sysprocesses during one of the sluggish
periods to see what it running. You could be experiencing blocking, or
just a poorly optimized query that is slowing things down.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you all for the responses, I appreciate the input. Sounds like it is
not worth my time.
Our server only runs SQL server and an instance of Backup Exec in SQL, other
than that, it runs nothing.
I think it is more due to the application than the server portion now anyway.
--
Thanks, Jeff
"Tracy McKibben" wrote:
> Jeff wrote:
> > hello,
> >
> > I have a single, dual-processor SQL server running our companies primary
> > application for 60 users. We are running SQL 2000 sp4 on 2000 Server, sp4.
> > Server access via the application seems sluggish at times and I am wondering
> > if boosting the SQL Priority will help in this regard.
> >
> > Can someone provide some details on the pro's and con's of enabling this?
> >
> > Also, what benefit would adding the instance of SQL to Active Directory
> > provide?
> >
> >
> More than likely, boosting the priority won't help you out at all. You
> should start by looking at sysprocesses during one of the sluggish
> periods to see what it running. You could be experiencing blocking, or
> just a poorly optimized query that is slowing things down.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Boost SQL Priority Pros and Cons

hello,
I have a single, dual-processor SQL server running our companies primary
application for 60 users. We are running SQL 2000 sp4 on 2000 Server, sp4.
Server access via the application seems sluggish at times and I am wondering
if boosting the SQL Priority will help in this regard.
Can someone provide some details on the pro's and con's of enabling this?
Also, what benefit would adding the instance of SQL to Active Directory
provide?
Thanks, Jeff"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:3E28C261-C90B-4BA1-AD6A-898AEE7B09BF@.microsoft.com...
> hello,
> I have a single, dual-processor SQL server running our companies primary
> application for 60 users. We are running SQL 2000 sp4 on 2000 Server,
> sp4.
> Server access via the application seems sluggish at times and I am
> wondering
> if boosting the SQL Priority will help in this regard.
> Can someone provide some details on the pro's and con's of enabling this?
>
If there are no other applciations running on the server, booting priority
will do nothing. If there are other application running on the server using
lots of CPU, consider using Windows Server Resource Manager to allocate CPU.
It's much more flexible, smarter and safer than messing with process
priority. T

> Also, what benefit would adding the instance of SQL to Active Directory
> provide?
>
None.
David|||If you have performance problems, looking at changing
configuration settings is generally one of the last things
you would typically look at. Many of the times that people
change those settings, it just causes more harm than good.
It's pretty rare to ever need to change the priority.
The following is a pretty good short article on the
configuration settings:
How to determine proper SQL Server configuration settings
http://support.microsoft.com/?id=319942
-Sue
On Thu, 27 Jul 2006 15:04:01 -0700, Jeff
<Jeff@.discussions.microsoft.com> wrote:

>hello,
>I have a single, dual-processor SQL server running our companies primary
>application for 60 users. We are running SQL 2000 sp4 on 2000 Server, sp4.
>Server access via the application seems sluggish at times and I am wonderin
g
>if boosting the SQL Priority will help in this regard.
>Can someone provide some details on the pro's and con's of enabling this?
>Also, what benefit would adding the instance of SQL to Active Directory
>provide?|||Jeff wrote:
> hello,
> I have a single, dual-processor SQL server running our companies primary
> application for 60 users. We are running SQL 2000 sp4 on 2000 Server, sp4
.
> Server access via the application seems sluggish at times and I am wonderi
ng
> if boosting the SQL Priority will help in this regard.
> Can someone provide some details on the pro's and con's of enabling this?
> Also, what benefit would adding the instance of SQL to Active Directory
> provide?
>
More than likely, boosting the priority won't help you out at all. You
should start by looking at sysprocesses during one of the sluggish
periods to see what it running. You could be experiencing blocking, or
just a poorly optimized query that is slowing things down.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you all for the responses, I appreciate the input. Sounds like it is
not worth my time.
Our server only runs SQL server and an instance of Backup Exec in SQL, other
than that, it runs nothing.
I think it is more due to the application than the server portion now anyway
.
Thanks, Jeff
"Tracy McKibben" wrote:

> Jeff wrote:
> More than likely, boosting the priority won't help you out at all. You
> should start by looking at sysprocesses during one of the sluggish
> periods to see what it running. You could be experiencing blocking, or
> just a poorly optimized query that is slowing things down.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>