SQl job that runs for long

  • Hi,

    We have a SQL job that runs for about 13-14 hours and I am just wondering if its okay? or is it normal ?

    (its has lot of table records updates which does it by cursors)

  • That's a job that I would look to tune right away.

    Is it possible that some job out there could realistically run that long? Sure. But it depends on quantity of data and whether or not it is an ETL type job.

    But, when you say it is doing something via cursor and it runs for that long, I bet it could be tuned and could run faster.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply