Nightly Jobs

SQLServerCentral Article

Never update systems tables directly - a study in Agent job scheduling

  • Article

It is often recommended that system tables should not be updated directly. Presenting a case in point built around nightly job configuration in order to demonstrate the possible issues with updating system tables directly.

4.44 (16)

You rated this post out of 5. Change rating

2012-09-17

5,247 reads

Technical Article

RE: Generate Sequence Number Safely

  • Reply

Another approach is to use another table to hold your values. Then use a stored procedure to update the other table and get the last value. Always get your values through this stored procedure. The procedure should put an update lock on the row of the table (you can manage many keys in the same […]

You rated this post out of 5. Change rating

2003-12-29

Blogs

Enabling an Index: #SQLNewBlogger

By

I don’t do a lot of work with disabled index, but I learned how...

Back to Boston for SQL Saturday

By

I’m leaving again tomorrow for a trip. This time I head back to Boston...

T-SQL Tuesday #179: What’s In Your Data Detective Toolkit?

By

Most of us who work with data have, at least a few times, been...

Read the latest Blogs

Forums

7 sept, scheduled book

By philip.scott

Comments posted to this topic are about the item 7 sept, scheduled book

7 sept, schedlued article

By philip.scott

Comments posted to this topic are about the item 7 sept, schedlued article

6 sept, published book

By philip.scott

Comments posted to this topic are about the item 6 sept, published book

Visit the forum

Question of the Day

Azure Data Lake Storage Gen 2

Azure Data Lake Storage Gen 2 is built on ...?

See possible answers