[dba-SQLServer]Running a Job

John -

I went thru and noticed the "Run as User" field was not consistent
throughout all steps.

When I ran the job again, all steps ran for about a second each.

I then created a job that contained only 1 step, and it took the full 30
minutes to run.

After going back and forth for a while, it seems that when the sproc
contains code to execute a package, it pretty much skips it in the job.
The sproc that ran normally contained an action query, but the sproc
that didn't do anything contained xp_cmdshell code to run a DTS package.

Is there a special way to set up a job that runs DTS packages?

 

Mark

 

 

-----Original Message-----
From: DJK(John) Robinson [mailto:djkr at msn.com] 
Sent: Monday, August 11, 2003 10:17 AM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer]Running a Job

 

OK - and 30 minutes would certainly be noticeable!

 

I'm working a bit in the dark, of course, but what I would check next is
that each Jobstep is running in the database you expect (on the General
tab) and, on its Advanced tab, that its "Run as User:" is the one you
intend.

 

Have you, for instance developed the jobstep's SP in one database and
then transferred it to the production DB?  ... perhaps not catering for
dummy/earlier versions, permissions, or somesuch?

 

Does each SP run OK in QA in a similar environment?

 

(Clutching at straws, really, but just thinking of mistakes I have
made!)

John

 

	-----Original Message-----
	From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mark
Boyd
	Sent: 11 August 2003 14:17
	To: dba-sqlserver at databaseadvisors.com
	Subject: RE: [dba-SQLServer]Running a Job

	John -

	It tells me that all steps have succeeded.

	I know the sprocs aren't running because normally they each take
about 30 minutes to run.

	When I run the sprocs in a job, they each run for about a
second, then return successful.

	 

	Mark

	 

	-----Original Message-----
	From: DJK(John) Robinson [mailto:djkr at msn.com] 
	Sent: Saturday, August 09, 2003 4:20 AM
	To: dba-sqlserver at databaseadvisors.com
	Subject: RE: [dba-SQLServer]Running a Job

	 

	Mark

	 

	In the Job History, have you checked whether any/all of the
individual job steps have succeeded?

	 

	John

	 

		-----Original Message-----
		From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mark
Boyd
		Sent: 08 August 2003 19:15
		To: dba-sqlserver at databaseadvisors.com
		Subject: RE: [dba-SQLServer]Running a Job

		Eric -

		The job history is telling me it succeeded, but I can
tell the sprocs in the steps didn't execute.

		 

		Mark

		 

		-----Original Message-----
		From: Eric Barro [mailto:ebarro at afsweb.com] 
		Sent: Friday, August 08, 2003 12:06 PM
		To: dba-sqlserver at databaseadvisors.com
		Subject: RE: [dba-SQLServer]Running a Job

		 

		Mark,

		 

		Check the Job History details to see if it succeeded or
failed.

		 

		---
		Eric Barro
		Senior Systems Analyst
		Advanced Field Services
		(208) 772-7060
		http://www.afsweb.com <http://www.afsweb.com/>  

			-----Original Message-----
			From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Mark
Boyd
			Sent: Friday, August 08, 2003 8:52 AM
			To: SQLServerList
			Subject: [dba-SQLServer]Running a Job

			I am attempting to run a job thru SQL2000
Enterprise Mgr.

			This job consists of 6 steps, each containing a
sproc in the command.

			When I go to run the job, it finishes
successfully in about 5 seconds, but doesn't seem to run any of the
sprocs.

			Each step looks like the following: execute
spSproc.

			Am I missing something?

			Any ideas?

			 

			TIA,

			Mark Boyd

			Sr. Systems Analyst

			McBee Associates, Inc.

			 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/dba-sqlserver/attachments/20030811/6e1079ca/attachment.html>