I have a Job on our SQL Sever 2008 that executes stored procedure in every hour. The stored procedures aggregates data from one database to another
applying some business rules on it to a SQL Server database. On average it takes about 3 minutes to run the job. But if job takes for more than an hour, then, another job starts and start running aggregation on same set of data. Thus, aggregated number is
duplicated/more than the original number of records. How can I setup the job in a way if the job is still running after 50 minutes then stop the job? Or is there a better way to avoid the job from running nonstop and hitting the data integrity?
View Complete Post