Hi People, I'm facing a very strange situation !
I recently imported some jobs using a script and I
realized that all the steps are out of order when I click
on start job, for example I HAVE 4 steps and it shows like
this 4 - 2 - 3 - 1 ! WHAT IS THAT '
I also notice that when I create new JOBS all order for
the steps are wrong ! WHATA IS THAT JESUS !
Please HELP ME ! THANK'S !
.I bet you installed the MS03_031 SQL Server Patch. After
I installed this patch I had the same problem. You / we
will need to wait till the next patch. :(
-Stephen
>--Original Message--
>I know this isn't what you looking for but can you
reorder them? have you
>change your sort order in sql?
>
>Yovan Fernandez
>"Roberto Carrasco" <Roberto_carrasco@.msn.com> wrote in
message
>news:058601c377d8$151d5130$a101280a@.phx.gbl...
>> Hi People, I'm facing a very strange situation !
>> I recently imported some jobs using a script and I
>> realized that all the steps are out of order when I
click
>> on start job, for example I HAVE 4 steps and it shows
like
>> this 4 - 2 - 3 - 1 ! WHAT IS THAT '
>> I also notice that when I create new JOBS all order for
>> the steps are wrong ! WHATA IS THAT JESUS !
>> Please HELP ME ! THANK'S !
>> .
>>
>
>.
>|||Hi,
I Installed ! Jesus ! This is terrible ! This kind of
thing that happen, very sad.
We wait !
Thank's !
>--Original Message--
>I bet you installed the MS03_031 SQL Server Patch. After
>I installed this patch I had the same problem. You / we
>will need to wait till the next patch. :(
>-Stephen
>>--Original Message--
>>I know this isn't what you looking for but can you
>reorder them? have you
>>change your sort order in sql?
>>
>>Yovan Fernandez
>>"Roberto Carrasco" <Roberto_carrasco@.msn.com> wrote in
>message
>>news:058601c377d8$151d5130$a101280a@.phx.gbl...
>> Hi People, I'm facing a very strange situation !
>> I recently imported some jobs using a script and I
>> realized that all the steps are out of order when I
>click
>> on start job, for example I HAVE 4 steps and it shows
>like
>> this 4 - 2 - 3 - 1 ! WHAT IS THAT '
>> I also notice that when I create new JOBS all order for
>> the steps are wrong ! WHATA IS THAT JESUS !
>> Please HELP ME ! THANK'S !
>> .
>>
>>
>>.
>.
>|||I am having the same problem. Were you able to fins a solution?
Ashwin Mahaja
--
amahaja
----
amahajan's Profile: http://www.msusenet.com/member.php?userid=39
View this thread: http://www.msusenet.com/t-322648
Showing posts with label situation. Show all posts
Showing posts with label situation. Show all posts
Wednesday, March 28, 2012
Friday, March 9, 2012
Job Execution "Failed"
Hello,
I've created one job, sometimes after the job has been
started, the job stays frozen(the job never ends). To
resolve this situation i need to restart SQL Server Agent.
I would like to develope one script or create one alert
that tell me information when this job get frozen again
but.. i dont know how. I try to check information in the
msdb..sysjobschedules but i cant do anything to reslve
this situation with the info returned.
Help me.. thanks
Best RegardsI'm not sure if there's any out of the box feature that does that, but in
case no one comes up with anything better, you could implement a log table
that tracks the progress of the package and have another package dedicated
to reading the log & sending alerts if a package takes too long. This might
be a kludge, but it would at least be flexible and allow you to check step
execution timings etc.
Regards,
Greg Linwood
SQL Server MVP
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:c0ac01c4382d$488fe490$a301280a@.phx.gbl...
> Hello,
> I've created one job, sometimes after the job has been
> started, the job stays frozen(the job never ends). To
> resolve this situation i need to restart SQL Server Agent.
> I would like to develope one script or create one alert
> that tell me information when this job get frozen again
> but.. i dont know how. I try to check information in the
> msdb..sysjobschedules but i cant do anything to reslve
> this situation with the info returned.
> Help me.. thanks
> Best Regards
I've created one job, sometimes after the job has been
started, the job stays frozen(the job never ends). To
resolve this situation i need to restart SQL Server Agent.
I would like to develope one script or create one alert
that tell me information when this job get frozen again
but.. i dont know how. I try to check information in the
msdb..sysjobschedules but i cant do anything to reslve
this situation with the info returned.
Help me.. thanks
Best RegardsI'm not sure if there's any out of the box feature that does that, but in
case no one comes up with anything better, you could implement a log table
that tracks the progress of the package and have another package dedicated
to reading the log & sending alerts if a package takes too long. This might
be a kludge, but it would at least be flexible and allow you to check step
execution timings etc.
Regards,
Greg Linwood
SQL Server MVP
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:c0ac01c4382d$488fe490$a301280a@.phx.gbl...
> Hello,
> I've created one job, sometimes after the job has been
> started, the job stays frozen(the job never ends). To
> resolve this situation i need to restart SQL Server Agent.
> I would like to develope one script or create one alert
> that tell me information when this job get frozen again
> but.. i dont know how. I try to check information in the
> msdb..sysjobschedules but i cant do anything to reslve
> this situation with the info returned.
> Help me.. thanks
> Best Regards
Job Execution "Failed"
Hello,
I've created one job, sometimes after the job has been
started, the job stays frozen(the job never ends). To
resolve this situation i need to restart SQL Server Agent.
I would like to develope one script or create one alert
that tell me information when this job get frozen again
but.. i dont know how. I try to check information in the
msdb..sysjobschedules but i cant do anything to reslve
this situation with the info returned.
Help me.. thanks
Best RegardsI'm not sure if there's any out of the box feature that does that, but in
case no one comes up with anything better, you could implement a log table
that tracks the progress of the package and have another package dedicated
to reading the log & sending alerts if a package takes too long. This might
be a kludge, but it would at least be flexible and allow you to check step
execution timings etc.
Regards,
Greg Linwood
SQL Server MVP
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:c0ac01c4382d$488fe490$a301280a@.phx.gbl...
> Hello,
> I've created one job, sometimes after the job has been
> started, the job stays frozen(the job never ends). To
> resolve this situation i need to restart SQL Server Agent.
> I would like to develope one script or create one alert
> that tell me information when this job get frozen again
> but.. i dont know how. I try to check information in the
> msdb..sysjobschedules but i cant do anything to reslve
> this situation with the info returned.
> Help me.. thanks
> Best Regards
I've created one job, sometimes after the job has been
started, the job stays frozen(the job never ends). To
resolve this situation i need to restart SQL Server Agent.
I would like to develope one script or create one alert
that tell me information when this job get frozen again
but.. i dont know how. I try to check information in the
msdb..sysjobschedules but i cant do anything to reslve
this situation with the info returned.
Help me.. thanks
Best RegardsI'm not sure if there's any out of the box feature that does that, but in
case no one comes up with anything better, you could implement a log table
that tracks the progress of the package and have another package dedicated
to reading the log & sending alerts if a package takes too long. This might
be a kludge, but it would at least be flexible and allow you to check step
execution timings etc.
Regards,
Greg Linwood
SQL Server MVP
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:c0ac01c4382d$488fe490$a301280a@.phx.gbl...
> Hello,
> I've created one job, sometimes after the job has been
> started, the job stays frozen(the job never ends). To
> resolve this situation i need to restart SQL Server Agent.
> I would like to develope one script or create one alert
> that tell me information when this job get frozen again
> but.. i dont know how. I try to check information in the
> msdb..sysjobschedules but i cant do anything to reslve
> this situation with the info returned.
> Help me.. thanks
> Best Regards
Job Execution "Failed"
Hello,
I've created one job, sometimes after the job has been
started, the job stays frozen(the job never ends). To
resolve this situation i need to restart SQL Server Agent.
I would like to develope one script or create one alert
that tell me information when this job get frozen again
but.. i dont know how. I try to check information in the
msdb..sysjobschedules but i cant do anything to reslve
this situation with the info returned.
Help me.. thanks
Best Regards
I'm not sure if there's any out of the box feature that does that, but in
case no one comes up with anything better, you could implement a log table
that tracks the progress of the package and have another package dedicated
to reading the log & sending alerts if a package takes too long. This might
be a kludge, but it would at least be flexible and allow you to check step
execution timings etc.
Regards,
Greg Linwood
SQL Server MVP
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:c0ac01c4382d$488fe490$a301280a@.phx.gbl...
> Hello,
> I've created one job, sometimes after the job has been
> started, the job stays frozen(the job never ends). To
> resolve this situation i need to restart SQL Server Agent.
> I would like to develope one script or create one alert
> that tell me information when this job get frozen again
> but.. i dont know how. I try to check information in the
> msdb..sysjobschedules but i cant do anything to reslve
> this situation with the info returned.
> Help me.. thanks
> Best Regards
I've created one job, sometimes after the job has been
started, the job stays frozen(the job never ends). To
resolve this situation i need to restart SQL Server Agent.
I would like to develope one script or create one alert
that tell me information when this job get frozen again
but.. i dont know how. I try to check information in the
msdb..sysjobschedules but i cant do anything to reslve
this situation with the info returned.
Help me.. thanks
Best Regards
I'm not sure if there's any out of the box feature that does that, but in
case no one comes up with anything better, you could implement a log table
that tracks the progress of the package and have another package dedicated
to reading the log & sending alerts if a package takes too long. This might
be a kludge, but it would at least be flexible and allow you to check step
execution timings etc.
Regards,
Greg Linwood
SQL Server MVP
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:c0ac01c4382d$488fe490$a301280a@.phx.gbl...
> Hello,
> I've created one job, sometimes after the job has been
> started, the job stays frozen(the job never ends). To
> resolve this situation i need to restart SQL Server Agent.
> I would like to develope one script or create one alert
> that tell me information when this job get frozen again
> but.. i dont know how. I try to check information in the
> msdb..sysjobschedules but i cant do anything to reslve
> this situation with the info returned.
> Help me.. thanks
> Best Regards
Subscribe to:
Posts (Atom)