Job step + linked server help

I have a job step that executes a lot of stored procs against linked servers
such as
exec server1.db.dbo.abc
exec server2.db.dbo.abc
exec server3.db.dbo.abc
exec server4.db.dbo.abc
I do not wish to create multiple job steps but would like to know
programatically how i can run all those statements even if say linked server
server2 is unavailable. Currently if server2 is unavailable, it just exits
out. I would like for it to proceed and execute the last 2 stored procs for
server3 and server4TSQL jobsteps will exit if you get errors. You would have to talk to the person who wrote agent and
get a new compile to change that.
One alternative is to use a CMDExec jobstep and OSQL.EXE instead.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:%23WcbEJhkDHA.2328@.TK2MSFTNGP10.phx.gbl...
> I have a job step that executes a lot of stored procs against linked servers
> such as
> exec server1.db.dbo.abc
> exec server2.db.dbo.abc
> exec server3.db.dbo.abc
> exec server4.db.dbo.abc
> I do not wish to create multiple job steps but would like to know
> programatically how i can run all those statements even if say linked server
> server2 is unavailable. Currently if server2 is unavailable, it just exits
> out. I would like for it to proceed and execute the last 2 stored procs for
> server3 and server4
>
>|||Hassan
Check for PING to the server.
set nocount on
CREATE TABLE #t_ip (ip varchar(255))
DECLARE @.PingSql varchar(1000)
SELECT @.PingSql = 'ping ' + 00.00.0.0'
INSERT INTO #t_ip EXEC master.dbo.xp_cmdshell @.PingSql
SELECT * FROM #t_ip
IF EXISTS (SELECT TOP 2 * FROM #t_ip WHERE IP = 'Request timed out' )
BEGIN
..................
END
DROP TABLE #t_ip
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:#WcbEJhkDHA.2328@.TK2MSFTNGP10.phx.gbl...
> I have a job step that executes a lot of stored procs against linked
servers
> such as
> exec server1.db.dbo.abc
> exec server2.db.dbo.abc
> exec server3.db.dbo.abc
> exec server4.db.dbo.abc
> I do not wish to create multiple job steps but would like to know
> programatically how i can run all those statements even if say linked
server
> server2 is unavailable. Currently if server2 is unavailable, it just exits
> out. I would like for it to proceed and execute the last 2 stored procs
for
> server3 and server4
>
>

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.
How many times are you going to post this question?
http://www.aspfaq.com/
(Reverse address to reply.)
"Mark - HYPERe" <MarkHYPERe@.discussions.microsoft.com> wrote in message
news:A6CBF4C4-0889-4526-91EA-BB325D99D859@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.
Ideally, it should take around the same amount of time. But are there any
logs in the sqlagent.out that might point to some errors or weird behaviour?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.
Ownership issues? Why did you leave the table owner name blank (you should
always specify dbo if there is only one such table)? If you are dbo you are
going to see different plan, perhaps, than SQL Server agent (remember that
SQL Server Agent jobs do not execute in the same context as you are
currently logged in to Query Analyzer).
http://www.aspfaq.com/
(Reverse address to reply.)
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.
|||Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 to
see if it applies:
http://support.microsoft.com/default...30&Product=sql
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.
|||Thanks - that worked. Cheers to you. Sorry about the multiple posts. I was getting error messages when posting.
"Dan Guzman" wrote:

> Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 to
> see if it applies:
> http://support.microsoft.com/default...30&Product=sql
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
> news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> analyzer. If I run it from a job it takes 17.5061 minutes.
> dog. Are jobs governed. No other variables to consider - on a standalone
> network using the same box. The proc performs a series of updates, deletes,
> and inserts.
>
>
|||> Thanks - that worked. Cheers to you. Sorry about the multiple posts. I
was getting error messages when posting.
http://www.aspfaq.com/5007
sql

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.Ownership issues? Why did you leave the table owner name blank (you should
always specify dbo if there is only one such table)? If you are dbo you are
going to see different plan, perhaps, than SQL Server agent (remember that
SQL Server Agent jobs do not execute in the same context as you are
currently logged in to Query Analyzer).
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.|||Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 to
see if it applies:
http://support.microsoft.com/default.aspx?scid=kb;en-us;249730&Product=sql
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.|||> Thanks - that worked. Cheers to you. Sorry about the multiple posts. I
was getting error messages when posting.
http://www.aspfaq.com/5007

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.Ideally, it should take around the same amount of time. But are there any
logs in the sqlagent.out that might point to some errors or weird behaviour?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer.
If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog.
Are jobs governed. No other variables to consider - on a standalone networ
k using the same box. The proc performs a series of updates, deletes, and i
nserts.
Thank you for your help.Ownership issues? Why did you leave the table owner name blank (you should
always specify dbo if there is only one such table)? If you are dbo you are
going to see different plan, perhaps, than SQL Server agent (remember that
SQL Server Agent jobs do not execute in the same context as you are
currently logged in to Query Analyzer).
http://www.aspfaq.com/
(Reverse address to reply.)
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.|||Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 to
see if it applies:
http://support.microsoft.com/defaul...730&Product=sql
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.|||Thanks - that worked. Cheers to you. Sorry about the multiple posts. I wa
s getting error messages when posting.
"Dan Guzman" wrote:

> Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 t
o
> see if it applies:
> http://support.microsoft.com/defaul...730&Product=sql
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
> news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> analyzer. If I run it from a job it takes 17.5061 minutes.
> dog. Are jobs governed. No other variables to consider - on a standalone
> network using the same box. The proc performs a series of updates, delete
s,
> and inserts.
>
>|||> Thanks - that worked. Cheers to you. Sorry about the multiple posts. I
was getting error messages when posting.
http://www.aspfaq.com/5007

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer.
If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog.
Are jobs governed. No other variables to consider - on a standalone networ
k using the same box. The proc performs a series of updates, deletes, and i
nserts.
Thank you for your help.Ideally, it should take around the same amount of time. But are there any
logs in the sqlagent.out that might point to some errors or weird behaviour?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.