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

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

Posted on SQL Server Central See other posts from SQL Server Central
Published on Mon, 17 Sep 2012 06:00:00 UT Indexed on 2012/09/19 21:45 UTC
Read the original article Hit count: 324

Filed under:

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.

SQL Monitor What can SQL Monitor 3.2 monitor?
Whatever you think is most important. Use custom metrics to monitor and alert on data that's most important for your environment. Find out more.

© SQL Server Central or respective owner

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

Categories cloud

.NET ASP.NET iphone linux python Windows mysql android sql windows-7 html c ruby-on-rails css objective-c ubuntu networking sql-server wpf asp.net-mvc ruby database Xml apache AJAX osx security regex django Performance 12.04 windows-xp mac web-development iphone-sdk vb.net Silverlight apache2 flash server perl best-practices email installation eclipse visual-studio algorithm windows-server-2008 winforms wcf firefox bash dns /Oracle