Boot.ini file: machines

Showing posts with label machines. Show all posts

Sunday, March 11, 2012

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

Sunday, February 12, 2012

BPA Feedback and Question

I've been exploring the best practices tool and find most things great! I have installed it on multiple machines and then changed the database that each client logs into to be the same one so that we have one central repository and it seems to be working
well. I would like to see a way to schedule a job that would run the scans at off hours since we are trying to make it mandatory for our developers to run a clean scan before they move out of our development environment. I was also surprised when i not
iced that there were no stored procedures in the slqbpa database, isn't that going against best practices ;)
Debi
In the released version there will be a command line version that will let
you use sql agent or some other scheduler to do what you want.
About stored procedures... not that strictly a best practice... depends on
your application or on what you're trying to do. The extensible architecture
of bpa called for some adhoc query building which may be better in the app
than doing dynamic sql inside stored procs. That said, I would like to see
some of the logic moved to stored procs, post v1. In the pre-7.0 days,
stored procs were way more a perf best practice.
- Christian
___________________________
Christian Kleinerman
Program Manager, SQL Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Debi" <anonymous@.discussions.microsoft.com> wrote in message
news:B924F619-4B1C-4657-B61B-41DA672541CE@.microsoft.com...
> I've been exploring the best practices tool and find most things great! I
have installed it on multiple machines and then changed the database that
each client logs into to be the same one so that we have one central
repository and it seems to be working well. I would like to see a way to
schedule a job that would run the scans at off hours since we are trying to
make it mandatory for our developers to run a clean scan before they move
out of our development environment. I was also surprised when i noticed
that there were no stored procedures in the slqbpa database, isn't that
going against best practices ;)
|||Hello Debi,
how did you manage this?
I tried to install BPA on different machines...
but the tool doesn't support the same database for the different
installations.
did you install BPA on different machines with different databases?
what did you do with these databases - drop them?
how did you change the database to connect to?
Thanks Thomas
"Debi" wrote:

> I've been exploring the best practices tool and find most things great! I have installed it on multiple machines and then changed the database that each client logs into to be the same one so that we have one central repository and it seems to be worki
ng well. I would like to see a way to schedule a job that would run the scans at off hours since we are trying to make it mandatory for our developers to run a clean scan before they move out of our development environment. I was also surprised when i n
oticed that there were no stored procedures in the slqbpa database, isn't that going against best practices ;)
|||Have a look at http://www.sqldbatips.com/showarticle.asp?ID=9
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
"Mueller-Lynch Thomas" <MuellerLynchThomas@.discussions.microsoft.com> wrote
in message news:1EBAEBEF-38D1-471A-B277-B685AE3EB4BE@.microsoft.com...[vbcol=seagreen]
> Hello Debi,
> how did you manage this?
> I tried to install BPA on different machines...
> but the tool doesn't support the same database for the different
> installations.
> did you install BPA on different machines with different databases?
> what did you do with these databases - drop them?
> how did you change the database to connect to?
> Thanks Thomas
> "Debi" wrote:

Sunday, March 11, 2012

Bug in SP4

Bug in SP4

Bug in SP4

Sunday, February 12, 2012

BPA Feedback and Question

Boot.ini file

Blog Archive

About Me