I think I know the answer to my question, but I thought I would ask to be
sure that I'm correct. I have a need to run a job every 30 seconds, but the
Job Scheduler only gives the option of a frequency of 1 minute. Is there
anyway to set this up that way?Try this link:
http://www.sqldev.net/sqlagent/SQLAgentRecuringJobsInSecs.htm
"Big Ern" wrote:
> I think I know the answer to my question, but I thought I would ask to be
> sure that I'm correct. I have a need to run a job every 30 seconds, but the
> Job Scheduler only gives the option of a frequency of 1 minute. Is there
> anyway to set this up that way?
>
Showing posts with label seconds. Show all posts
Showing posts with label seconds. Show all posts
Monday, March 26, 2012
job scheduling
Hello,
Is it possible to schedule the sql agent to run a job every so many
seconds? I may have a need to schedule a job at a certain interval of
seconds and the sql agent gui scheduler seems to only allow scheduling
by the minute or more.
Thanks,
Greghttp://sqldev.net/sqlagent/SQLAgentRecuringJobsInSecs.htm
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Greg" <gjackson@.thq.com> wrote in message news:d9ii90l53hekbeg32g0cfcmfhavuak1dm5@.4ax.com...
> Hello,
> Is it possible to schedule the sql agent to run a job every so many
> seconds? I may have a need to schedule a job at a certain interval of
> seconds and the sql agent gui scheduler seems to only allow scheduling
> by the minute or more.
> Thanks,
> Greg|||If you are going to have something run every so many seconds you might
consider having a never ending stored procedure that uses the WAITFOR DELAY
command to control your running of some commands every few seconds.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Greg" <gjackson@.thq.com> wrote in message
news:d9ii90l53hekbeg32g0cfcmfhavuak1dm5@.4ax.com...
> Hello,
> Is it possible to schedule the sql agent to run a job every so many
> seconds? I may have a need to schedule a job at a certain interval of
> seconds and the sql agent gui scheduler seems to only allow scheduling
> by the minute or more.
> Thanks,
> Greg
Is it possible to schedule the sql agent to run a job every so many
seconds? I may have a need to schedule a job at a certain interval of
seconds and the sql agent gui scheduler seems to only allow scheduling
by the minute or more.
Thanks,
Greghttp://sqldev.net/sqlagent/SQLAgentRecuringJobsInSecs.htm
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Greg" <gjackson@.thq.com> wrote in message news:d9ii90l53hekbeg32g0cfcmfhavuak1dm5@.4ax.com...
> Hello,
> Is it possible to schedule the sql agent to run a job every so many
> seconds? I may have a need to schedule a job at a certain interval of
> seconds and the sql agent gui scheduler seems to only allow scheduling
> by the minute or more.
> Thanks,
> Greg|||If you are going to have something run every so many seconds you might
consider having a never ending stored procedure that uses the WAITFOR DELAY
command to control your running of some commands every few seconds.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Greg" <gjackson@.thq.com> wrote in message
news:d9ii90l53hekbeg32g0cfcmfhavuak1dm5@.4ax.com...
> Hello,
> Is it possible to schedule the sql agent to run a job every so many
> seconds? I may have a need to schedule a job at a certain interval of
> seconds and the sql agent gui scheduler seems to only allow scheduling
> by the minute or more.
> Thanks,
> Greg
Job Schedule.
Hi to all,
does anyone knows how to schedule a job to run in seconds time interval ?
I have found the sysobschedule table in msdb but even if i change the
freq_subday_type to 2 (seconds) the job doesn't run in seconds.
The only solution i imagine is to run once the Stored Procedure i want
and add a WAITFOR DELAY '00:00.05' command,
so this will run it constantly (and for ever...)
Is there any other way to accomplish the same thing,
or are there any side effects to have an sp to run forever
with the WAITFOR statement '
Thanks a lot for any help!
Anthony BoudouvasGert Drapers posted an undocumented way around this
limitation awhile back- it sounds like you had the right
idea on how to go about it, maybe something just got missed
in how you implemented it. Check the following example:
http://tinyurl.com/q0vv
-Sue
On Tue, 7 Oct 2003 13:08:59 +0200, "Anthony Boudouvas"
<anthonyb@.mediatel.gr> wrote:
>Hi to all,
>does anyone knows how to schedule a job to run in seconds time interval ?
>I have found the sysobschedule table in msdb but even if i change the
>freq_subday_type to 2 (seconds) the job doesn't run in seconds.
>The only solution i imagine is to run once the Stored Procedure i want
>and add a WAITFOR DELAY '00:00.05' command,
>so this will run it constantly (and for ever...)
>Is there any other way to accomplish the same thing,
>or are there any side effects to have an sp to run forever
>with the WAITFOR statement '
>
>Thanks a lot for any help!
>Anthony Boudouvas
>|||Ok, it did work that way.
Thanks a lot!
anthonyb
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:2aj5ov8bk7klsmgf79hgn70285g8fk112i@.4ax.com...
> Gert Drapers posted an undocumented way around this
> limitation awhile back- it sounds like you had the right
> idea on how to go about it, maybe something just got missed
> in how you implemented it. Check the following example:
> http://tinyurl.com/q0vv
> -Sue
> On Tue, 7 Oct 2003 13:08:59 +0200, "Anthony Boudouvas"
> <anthonyb@.mediatel.gr> wrote:
> >Hi to all,
> >
> >does anyone knows how to schedule a job to run in seconds time interval ?
> >I have found the sysobschedule table in msdb but even if i change the
> >freq_subday_type to 2 (seconds) the job doesn't run in seconds.
> >
> >The only solution i imagine is to run once the Stored Procedure i want
> >and add a WAITFOR DELAY '00:00.05' command,
> >so this will run it constantly (and for ever...)
> >
> >Is there any other way to accomplish the same thing,
> >or are there any side effects to have an sp to run forever
> >with the WAITFOR statement '
> >
> >
> >Thanks a lot for any help!
> >
> >Anthony Boudouvas
> >
>
does anyone knows how to schedule a job to run in seconds time interval ?
I have found the sysobschedule table in msdb but even if i change the
freq_subday_type to 2 (seconds) the job doesn't run in seconds.
The only solution i imagine is to run once the Stored Procedure i want
and add a WAITFOR DELAY '00:00.05' command,
so this will run it constantly (and for ever...)
Is there any other way to accomplish the same thing,
or are there any side effects to have an sp to run forever
with the WAITFOR statement '
Thanks a lot for any help!
Anthony BoudouvasGert Drapers posted an undocumented way around this
limitation awhile back- it sounds like you had the right
idea on how to go about it, maybe something just got missed
in how you implemented it. Check the following example:
http://tinyurl.com/q0vv
-Sue
On Tue, 7 Oct 2003 13:08:59 +0200, "Anthony Boudouvas"
<anthonyb@.mediatel.gr> wrote:
>Hi to all,
>does anyone knows how to schedule a job to run in seconds time interval ?
>I have found the sysobschedule table in msdb but even if i change the
>freq_subday_type to 2 (seconds) the job doesn't run in seconds.
>The only solution i imagine is to run once the Stored Procedure i want
>and add a WAITFOR DELAY '00:00.05' command,
>so this will run it constantly (and for ever...)
>Is there any other way to accomplish the same thing,
>or are there any side effects to have an sp to run forever
>with the WAITFOR statement '
>
>Thanks a lot for any help!
>Anthony Boudouvas
>|||Ok, it did work that way.
Thanks a lot!
anthonyb
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:2aj5ov8bk7klsmgf79hgn70285g8fk112i@.4ax.com...
> Gert Drapers posted an undocumented way around this
> limitation awhile back- it sounds like you had the right
> idea on how to go about it, maybe something just got missed
> in how you implemented it. Check the following example:
> http://tinyurl.com/q0vv
> -Sue
> On Tue, 7 Oct 2003 13:08:59 +0200, "Anthony Boudouvas"
> <anthonyb@.mediatel.gr> wrote:
> >Hi to all,
> >
> >does anyone knows how to schedule a job to run in seconds time interval ?
> >I have found the sysobschedule table in msdb but even if i change the
> >freq_subday_type to 2 (seconds) the job doesn't run in seconds.
> >
> >The only solution i imagine is to run once the Stored Procedure i want
> >and add a WAITFOR DELAY '00:00.05' command,
> >so this will run it constantly (and for ever...)
> >
> >Is there any other way to accomplish the same thing,
> >or are there any side effects to have an sp to run forever
> >with the WAITFOR statement '
> >
> >
> >Thanks a lot for any help!
> >
> >Anthony Boudouvas
> >
>
Friday, March 23, 2012
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.
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.
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
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
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.
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
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.
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.
Subscribe to:
Posts (Atom)