Drop Table
Support Forum for database administrators and web based access to important newsgroups related to databasesHi - I have one SQL job that run on schedule. This jobs normally takes 1 minute the most( It is simply truncating tables on other SQL server and populate data to those tables). One time it ran for almost more than 24 hours and I have to manually cancel it. This SQL job is schedule to run every day. Since The job status was running it did not kicked of next day. Since it did not failed so it did not notify me either. After cancelling it and then re running it worked fine Any one know any reason what could SQL server cause to run this job keep running. Thanks, Moh
Post Follow-up to this messageDid you run sp_who to see if the job spid is blocked? "Moh Abb" <mabbas@aligntech.com> wrote in message news:u44Q18AlFHA.2904@tk2msftngp13.phx.gbl... > Hi - I have one SQL job that run on schedule. This jobs normally takes 1 > minute the most( It is simply truncating tables on other SQL server and > populate data to those tables). One time it ran for almost more than 24 > hours and I have to manually cancel it. This SQL job is schedule to run > every day. Since The job status was running it did not kicked of next day. > Since it did not failed so it did not notify me either. > After cancelling it and then re running it worked fine > Any one know any reason what could SQL server cause to run this job keep > running. > > Thanks, > Moh > >
Post Follow-up to this messageIt was not. Moh "ChrisR" <noemail@bla.com> wrote in message news:O3HG8lFlFHA.3828@TK2MSFTNGP12.phx.gbl... > Did you run sp_who to see if the job spid is blocked? > > > "Moh Abb" <mabbas@aligntech.com> wrote in message > news:u44Q18AlFHA.2904@tk2msftngp13.phx.gbl... 1 day. > >
Post Follow-up to this message
Show a Printable Version
Email This Page to Someone!
Receive updates to this thread