January 28, 2010 at 7:29 pm
How much time it will take?
when I run on my personal DB,it completed in one minutes
but when i run on own product db,it took a long time ?
Who can tell me the reason~:-)
---------------------------------------
Thorn Bird...
January 28, 2010 at 10:42 pm
hey nplace6530 thx a lot for resolvinf this issue.
January 29, 2010 at 1:02 am
Hi,
I tried to populate a temp table via INSERT #jobs_status EXEC msdb.dbo.sp_help_job
but I have the following message :
"Server: Msg 8164, Level 16, State 1, Procedure sp_get_composite_job_info, Line 67
An INSERT EXEC statement cannot be nested. "
Any idea ???
Cheers,
Eric
PS : The temp Table was populated
January 29, 2010 at 1:10 am
eric, this error can be ignore as it will not affect the output.
one of the posts by nplace6530 has suggested replacing
INSERT #jobs_status EXEC msdb.dbo.sp_help_job
with
select sj.job_id, sj.name, sc.name as Category, sj.Enabled, sjs.last_run_outcome,
(select max(run_date) from sysjobhistory sjh where sjh.job_id = sj.job_id) as last_run_date
into #jobs_status
from sysjobs sj
join syscategories sc
on sj.category_id = sc.category_id
join msdb.dbo.sysjobservers sjs
on sjs.job_id = sj.job_id
January 29, 2010 at 2:48 am
Hi Ritesh
I forgot to say in my pervious post, thanks for this script. It was exactly what I was looking for and saved me quite a bit of work.
Many thanks!!!!
Nick.
January 29, 2010 at 4:11 am
Hey guys,
Require your help, While I am executing on the local server the script is running fine.
But when I try to execue the script on client production systems it is executing for indefinite time and when I forcefully stop execution I get the below error.....How to fix it.
"Msg 8164, Level 16, State 1, Procedure sp_get_composite_job_info, Line 72
An INSERT EXEC statement cannot be nested.
Query was cancelled by user.
"
January 29, 2010 at 4:44 am
you are welcome nplace6530 and I am happy to hear that its helping people 🙂
January 29, 2010 at 4:46 am
@chava.sreekanth: many others also reported performance issue. I guess its taking long time in section 6.. I will send the script excluding section 6 in a while try it and let me know
January 29, 2010 at 5:13 am
@chava.sreekanth: try this script, should work.... i read post where the issues was fixed by reducing the daterange for section 5. Section 5 returns backup history for 1 month. this version will return only 1 day histry...
January 29, 2010 at 6:28 am
Thank you,
I have executed the script, It is in the process of executing.....I will let you know once it gets executed.
But what is the estimated execution period?
Does it depend on no. of databases and their sizes?
Sreekanth
January 29, 2010 at 6:35 am
its really difficult to estimate exact execution time. it depends on lots of factors cpu, memory, number of jobs, databases... however if it is taking more than 30 seconds then it needs tuning . let me know ur server specs and time it took for execution
January 29, 2010 at 7:12 am
Thanks,
The provided Script has been executed.... it has taken 10 minutes approximate time.
But with the following warning :-
"Null value is eliminated by an aggregate or other SET operation"
What does it mean??
Execution time depends on what ??
January 29, 2010 at 9:14 am
I'm having problem w/2005 procedure this is executing. Haven't tried your updated code yet!!
Msg 8164, Level 16, State 1, Procedure sp_get_composite_job_info, Line 73
An INSERT EXEC statement cannot be nested.
January 29, 2010 at 6:18 pm
I don't think it is a good idea to use the xp_cmdshell to get the result on production DB.
It is other ways to achive the same reuslt?
A kind job by Ritesh Medhe,~ thx 🙂
---------------------------------------
Thorn Bird...
Viewing 15 posts - 76 through 90 (of 140 total)
You must be logged in to reply to this topic. Login to reply