InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 17:57:57 GMT20http://www.sqlservercentral.com/Forums/Topic1366409-391-1.aspxThanks Rich,I will look at this article now.Cheers,GeorgeThu, 04 Oct 2012 07:14:29 GMTgs1975http://www.sqlservercentral.com/Forums/Topic1366409-391-1.aspxYou're welcome, and thanks for replying!Nadrek's suggestion to look for untrusted FK constraints is a very good one. An untrusted FK constraint will be a performance killer, and they aren't obvious if you're not looking for them. If you're looking for some more information, [url=http://sqlblog.com/blogs/hugo_kornelis/archive/2007/03/29/can-you-trust-your-constraints.aspx]this is a great explanation and write-up describing the problem and the fix[/url].RichThu, 04 Oct 2012 07:02:49 GMTrmechaberhttp://www.sqlservercentral.com/Forums/Topic1366409-391-1.aspxThanks for all your replies. There's some really good jobs here that I had overlooked. I am just going through all of my servers and just want a number of jobs I can script out and run against all servers.All of your suggestions are most helpful.Thanks,GeorgeThu, 04 Oct 2012 06:36:45 GMTgs1975http://www.sqlservercentral.com/Forums/Topic1366409-391-1.aspxCheck for enabled but untrusted constraints.Log performance/error/etc information to a monitoring serverLog security information to a monitoring serverLog backup/agent job/error log information to a monitoring serverOptional: Restore a database backup as a test - if you don't do this, at minimum backup with CHECKSUM and then RESTORE VERIFYONLY, but that's still not as good as a real restore.Optional: check for disabled constraints.Wed, 03 Oct 2012 14:34:59 GMTNadrekhttp://www.sqlservercentral.com/Forums/Topic1366409-391-1.aspxWell that's pretty open-ended.... In no particular order, here's some of what I like to run:> You list "backups", but that will likely be at least 3 different jobs/schedules for FULL, DIFFERENTIAL, and LOG backups> I have a job that looks for failed Agent job steps and reports them to me, as a check on Agent jobs> I have a series of daily checks in one job: Autogrow events in the last 24 hours, critical DB sizes, DBs in FULL recovery mode that aren't in a specific list of DBs that should be, etc.> TempDB size tracking> Purge old records from msdb for things like backup runs, etc.> Find SQL backup files on disk that haven't gone off to tape via a network backup. This took a bit of work with CLR for me to set up, but I can now easily query the SQL backup drive for *.BAK files that have an archive bit set, which means they haven't been backed up to tape by our system backups.Does this help?RichTue, 02 Oct 2012 07:51:58 GMTrmechaberhttp://www.sqlservercentral.com/Forums/Topic1366409-391-1.aspx[url=http://crankydba.com/2012/07/28/seven-jobs-sqlsat126/]Seven SQL Agent Jobs you should be running[/url]Tue, 02 Oct 2012 07:48:45 GMTtim_harkinhttp://www.sqlservercentral.com/Forums/Topic1366409-391-1.aspxI normally create one for checking the error log as well (excluding information you don't need of course), has given me early warnings of corruption etc in the past and I wouldn't do without it now!! I also like to have some performance warnings from the built in metrics and alerts on error codes 17-25 + 823/824/825Simonhttp://www.simonrich.esTue, 02 Oct 2012 03:55:06 GMTBeastohttp://www.sqlservercentral.com/Forums/Topic1366409-391-1.aspxHi,What are the most common/best SQL Agent Jobs to set up?The ones I generally set up are as follows:- (Daily or weekly depending on job & circumstances)1.) Backing up databases2.) DBCC CheckDB Job3.) Disk Alerts4.) Rebuilding/Reorganising Indexes Based on Fragementation Level5.) Update Stats6.) Recycle Error_Log7.) Recycle Agent_Error_Log8.) Checking File Space of Selected DatabasesWhat other common jobs am I missing/should I be looking at?Kind regards,GeorgeMon, 01 Oct 2012 03:11:58 GMTgs1975