THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » SQL Server Agent   (RSS)
Showing page 2 of 3 (22 total posts)
  • Agent Alerts Management Pack updated

    I have updated the Agent Alerts Management Pack, cleaned up the T-SQL code which creates the alerts. You can now just copy, paste and execute that code. Earlier, for some of the some of the alert definitions it just generated the calls to the query result window, and you had to copy this to a query window and execute it. Now you just copy the code ...
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on September 15, 2011
  • Ola Hallengren's maint procedures now supports logging to table

    This can for instance be very useful if you want to keep track how long time things take, over time. Check them out here.Version history here.
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on July 15, 2011
  • Article released about moving databases

    Just a short notice that I've released an article about moving databases between SQL Server instances: You find it at http://www.karaszi.com/SQLServer/info_moving_database.asp.
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on July 10, 2011
  • Connect Digest : 2011-03-26

    This week I have collected five important bugs involving Management Studio, and I hope you'll visit them, provide input and vote on the ones you think are worthwhile. #651176 : SSMS tries to access disconnected network drives when in the Save File As wizardPaul Randal (blog | twitter) filed this issue when he experienced significant delays trying ...
    Posted to Aaron Bertrand (Weblog) by AaronBertrand on March 26, 2011
  • Upgrading from Express Edition to Standard Edition

    Say you encounter an SQL Server which is Express Edition, and it really should have been some higher edition. Sounds familiar? It is common for me as a consultant to find plenty of SQL Servers at a customer's site. Many of the databases in these will be moved (typically using backup and restore) to a ''real'' SQL Server. But in some cases, ...
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on January 27, 2011
  • Ola Hallengren's maint procedures now supports exclusions

    Ola has a set of stored procedures to do maint operations, see http://ola.hallengren.com/. Ola has now updated them to support exclusions or inclusions of tables, indexes or even whole schemas from index rebuild/reorg. Check out http://ola.hallengren.com/Documentation.html#SelectingIndexes for info on how to define exclusions and ...
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on August 9, 2010
  • Updated article "Agent Alerts Management Pack"

    I've just updated the ''Agent Alerts Management Pack'' found here. I realize that some don't feel confident in reading and executing T-SQL code and they instead prefer to point & click in SSMS instead. So I added two tables with my suggestion on the severity levels and error numbers to define alerts for.
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on April 11, 2010
  • Using sa as owner for jobs and databases

    This blog is not about avoiding logging in using the sa login. Hopefully we all know about this, and work towards avoidning this practice. Instead I want to talk about using sa, but not to login (authenticate), but as owner for jobs and databases. I want keep these thing de-individualized - so we avoid things like person A leaving the company and ...
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on December 30, 2009
  • SQL Server Agent jobs and user contexts

    In what user context does a job run? I recently found myself in a forum discussion and gave my stock reply, later realizing that I haven't actually tested this for a long time (I used to demo this in class during 6.5 courses - when we actually had time for slight diversions). Lets start with my assumptions: Job owned by sysadmin, TSQL ...
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on September 19, 2009
  • Watch out for that autogrow bug

    Under some circumstances, autogrow for database files can be set to some 12000 percent. I think this is limited to SQL Server 2005 and for databases upgraded from SQL Server 2000 (I didn't bother to search - feel free to comment if you know). So, if you have a reasonably sized database and autogrow kicks in, you can do the maths and realize that ...
    Posted to Tibor Karaszi (Weblog) by TiborKaraszi on August 5, 2009
Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement