November 16, 2015 at 11:28 pm
Comments posted to this topic are about the item SQL Job Schedules
...
November 16, 2015 at 11:29 pm
This was removed by the editor as SPAM
November 17, 2015 at 4:56 am
Nice question, thanks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 17, 2015 at 5:29 am
An interesting one to be sure. Thanks.
November 17, 2015 at 6:32 am
Ok but why does it works like this under the hood? Why 20 minutes? Why on schedule?
msdn web page is not very chatty about it.
November 17, 2015 at 8:15 am
Megistal (11/17/2015)
Ok but why does it works like this under the hood? Why 20 minutes? Why on schedule?msdn web page is not very chatty about it.
Just what I was wondering.
November 18, 2015 at 12:05 am
Thanks for this interesting question. I have been able to answer it only because I have studied jobs ( and used them ) in September.
As several posters , I am surprised by this value ( 20 minutes ) which I am considering as short and maybe wasteful in resources but I am far to be a specialist of this topic that I have used scarcely since the 2008 / 2008 R2 versions.
November 18, 2015 at 4:32 am
That was new 4 me, thanx
Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant
November 18, 2015 at 11:26 am
patricklambin (11/18/2015)
Thanks for this interesting question. I have been able to answer it only because I have studied jobs ( and used them ) in September.As several posters , I am surprised by this value ( 20 minutes ) which I am considering as short and maybe wasteful in resources but I am far to be a specialist of this topic that I have used scarcely since the 2008 / 2008 R2 versions.
I was surprised in the opposite direction, as in, I wondered why this wouldn't be updated every time something changed, like a new job being scheduled, or a job finishing execution. Obviously not a server implementer here 🙂
November 19, 2015 at 1:21 am
patrickmcginnis59 10839 (11/18/2015)
patricklambin (11/18/2015)
Thanks for this interesting question. I have been able to answer it only because I have studied jobs ( and used them ) in September.As several posters , I am surprised by this value ( 20 minutes ) which I am considering as short and maybe wasteful in resources but I am far to be a specialist of this topic that I have used scarcely since the 2008 / 2008 R2 versions.
I was surprised in the opposite direction, as in, I wondered why this wouldn't be updated every time something changed, like a new job being scheduled, or a job finishing execution. Obviously not a server implementer here 🙂
As I wrote in my post , my knowledge of jobs is coming from the time I have installed my SQL Server 2008 ( not R2 ). As I am curious , I have used jobs to be not ignorant about this topic , but I have not used it since 2010 except a little on September. It is why I have written that I am far to be a specialist. About your reply , you gave good reasons which push me to consider that I have been wrong.
I will restart to use jobs later as I have several problems with an old application using SMO and I don't like to give up something before having tried to finish a task in the most full way ( even if perfection is impossible ).
Anyway , thank you to have pointed my error. I have learnt something today and that it is the most important point according to me.
Have a nice day
November 19, 2015 at 6:14 am
patricklambin (11/19/2015)
patrickmcginnis59 10839 (11/18/2015)
patricklambin (11/18/2015)
Thanks for this interesting question. I have been able to answer it only because I have studied jobs ( and used them ) in September.As several posters , I am surprised by this value ( 20 minutes ) which I am considering as short and maybe wasteful in resources but I am far to be a specialist of this topic that I have used scarcely since the 2008 / 2008 R2 versions.
I was surprised in the opposite direction, as in, I wondered why this wouldn't be updated every time something changed, like a new job being scheduled, or a job finishing execution. Obviously not a server implementer here 🙂
As I wrote in my post , my knowledge of jobs is coming from the time I have installed my SQL Server 2008 ( not R2 ). As I am curious , I have used jobs to be not ignorant about this topic , but I have not used it since 2010 except a little on September. It is why I have written that I am far to be a specialist. About your reply , you gave good reasons which push me to consider that I have been wrong.
I will restart to use jobs later as I have several problems with an old application using SMO and I don't like to give up something before having tried to finish a task in the most full way ( even if perfection is impossible ).
Anyway , thank you to have pointed my error. I have learnt something today and that it is the most important point according to me.
Have a nice day
I don't think you made any error though, because you got the question right and I didn't, so if anybody made an error it was obviously me 🙂 We both learnt today and that's what counts right?
November 23, 2015 at 2:09 pm
Megistal (11/17/2015)
Ok but why does it works like this under the hood? Why 20 minutes? Why on schedule?msdn web page is not very chatty about it.
I wondered that too.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply