<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Tibor Karaszi</title><link>http://sqlblog.com/blogs/tibor_karaszi/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>Express Edition revisited, focus on SSMS</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2013/01/30/express-edition-revisited-focus-on-ssms.aspx</link><pubDate>Wed, 30 Jan 2013 17:01:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:47398</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>3</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/47398.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=47398</wfw:commentRss><description>(Note: I have re-written parts of this post in the light of the comments that SP1 of 2012 include Complete tools.) I have decided to revisit the topic of whats included in Express Edition, with focus on the tools. I have a couple of reasons for this:...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2013/01/30/express-edition-revisited-focus-on-ssms.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=47398" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Tools/default.aspx">Tools</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Trace/default.aspx">Trace</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Express+Edition/default.aspx">Express Edition</category></item><item><title>Backup and the evil RETAINDAYS option</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2012/07/08/backup-and-the-evil-retaindays-option.aspx</link><pubDate>Sun, 08 Jul 2012 12:25:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:44226</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>4</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/44226.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=44226</wfw:commentRss><description>"So what bad has this option done?", you probably as yourself. Well, not much, but I find it evil because it confuses people, especially those new to SQL Server. I have many times seen people specifying something like 3, and expect SQL Server to keep...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2012/07/08/backup-and-the-evil-retaindays-option.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=44226" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Tools/default.aspx">Tools</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Backup/default.aspx">Backup</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Maintenance/default.aspx">Maintenance</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/datetime/default.aspx">datetime</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>Analyzing the errorlog</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2012/07/05/analyzing-the-errorlog.aspx</link><pubDate>Thu, 05 Jul 2012 11:53:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:44203</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>0</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/44203.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=44203</wfw:commentRss><description>How often do you do this? Look over each message (type) in the errorlog file and determine whether this is something you want to act on. Sure, some (but not all) of you have some monitoring solution in place, but are you 100% confident that it really...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2012/07/05/analyzing-the-errorlog.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=44203" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Tools/default.aspx">Tools</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Maintenance/default.aspx">Maintenance</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Installation/default.aspx">Installation</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Troubleshooting/default.aspx">Troubleshooting</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>List columns where collation doesn't match database collation</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2012/05/23/list-columns-where-collation-doesn-t-match-database-collation.aspx</link><pubDate>Wed, 23 May 2012 16:58:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:43522</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>1</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/43522.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=43522</wfw:commentRss><description>Below script lists all database/table/column where the column collation doesn't match the database collation. I just wrote it for a migration project and thought I'd share it. I'm sure lots of tings can be improved, but below worked just fine for me for...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2012/05/23/list-columns-where-collation-doesn-t-match-database-collation.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=43522" width="1" height="1"&gt;</description></item><item><title>Send email after Agent job execution</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/12/28/send-email-after-agent-job-execution.aspx</link><pubDate>Wed, 28 Dec 2011 11:15:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:40667</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>2</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/40667.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=40667</wfw:commentRss><description>After executing a job, I want to have an email with the following information: Success or failure in the mail subject (not just in the body) Success or failure and execution time for each job step in mail body Have output file(s) for the job steps attached...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/12/28/send-email-after-agent-job-execution.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=40667" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>SQL Live Monitor</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/11/19/sql-live-monitor.aspx</link><pubDate>Sat, 19 Nov 2011 08:46:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:39884</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>1</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/39884.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=39884</wfw:commentRss><description>I just found this one out there and wanted to share it. It connects to an instance and show you a bunch of figures. Nothing you can't extract yourself with SQL queries, but sometimes it is just nice to have one tool which is very easy to use. Here's what...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/11/19/sql-live-monitor.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=39884" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Tools/default.aspx">Tools</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Performance/default.aspx">Performance</category></item><item><title>Who owns your jobs?</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/10/06/who-owns-your-jobs.aspx</link><pubDate>Thu, 06 Oct 2011 16:13:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:38900</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>0</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/38900.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=38900</wfw:commentRss><description>Yep, another Agent blog. The topic of job owner has been discussed here before, but this is a specific situation, which potentially is a ticking bomb. First a quick recap of how agent does things: When a job is owned by somebody who is sysadmin, then...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/10/06/who-owns-your-jobs.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=38900" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Troubleshooting/default.aspx">Troubleshooting</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>Agent Alerts Management Pack updated</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/09/15/agent-alerts-management-pack-updated.aspx</link><pubDate>Thu, 15 Sep 2011 19:13:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:38484</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>7</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/38484.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=38484</wfw:commentRss><description>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...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/09/15/agent-alerts-management-pack-updated.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=38484" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>Ola Hallengren's maint procedures now supports logging to table</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/07/16/ola-hallengren-s-maint-procedures-now-supports-logging-to-table.aspx</link><pubDate>Sat, 16 Jul 2011 01:19:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:36985</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>1</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/36985.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=36985</wfw:commentRss><description>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 ....(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/07/16/ola-hallengren-s-maint-procedures-now-supports-logging-to-table.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=36985" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Tools/default.aspx">Tools</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Maintenance/default.aspx">Maintenance</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>Article released about moving databases</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/07/10/article-released-about-moving-databases.aspx</link><pubDate>Sun, 10 Jul 2011 13:26:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:36757</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>2</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/36757.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=36757</wfw:commentRss><description>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 ....(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/07/10/article-released-about-moving-databases.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=36757" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Maintenance/default.aspx">Maintenance</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Troubleshooting/default.aspx">Troubleshooting</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>Restricting memory using Resource Governor</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/04/19/restricting-memory-using-resource-governor.aspx</link><pubDate>Tue, 19 Apr 2011 11:13:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:35008</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>4</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/35008.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=35008</wfw:commentRss><description>You might know that Resource Governor (RG) can be used to allow you to affect resource allocation inside SQL Server. RG was introduced with SQL Server 2008 and requires Enterprise Edition or similar/higher. There are two things you can govern using RG:...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/04/19/restricting-memory-using-resource-governor.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=35008" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Performance/default.aspx">Performance</category></item><item><title>What does this Express Edition look like, anyhow?</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/02/10/what-does-this-express-edition-look-like-anyhow.aspx</link><pubDate>Thu, 10 Feb 2011 17:40:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:33378</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>5</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/33378.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=33378</wfw:commentRss><description>Chances are that you rarely get to see the Express Edition of SQL Server if you mainly work with servers. This blog post is inspired from a forum discussion where some functionality is missing in SQL Server Management Studio (SSMS) and I suspected that...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/02/10/what-does-this-express-edition-look-like-anyhow.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=33378" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Installation/default.aspx">Installation</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Express+Edition/default.aspx">Express Edition</category></item><item><title>Are we Borg?</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/02/09/are-we-borg.aspx</link><pubDate>Wed, 09 Feb 2011 20:47:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:33353</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>8</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/33353.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=33353</wfw:commentRss><description>Is it time to stop remeber things? For real, this time? Today I needed to find two pieces of SQL Server related information. One was straight foward, I posted it on #sqlhelp on twitter and a minute or so later I had the answer. The other was a bit more...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/02/09/are-we-borg.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=33353" width="1" height="1"&gt;</description></item><item><title>Upgrading from Express Edition to Standard Edition</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2011/01/27/upgrading-from-express-edition-to-standard-edition.aspx</link><pubDate>Thu, 27 Jan 2011 12:14:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:32952</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>7</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/32952.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=32952</wfw:commentRss><description>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...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2011/01/27/upgrading-from-express-edition-to-standard-edition.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=32952" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Installation/default.aspx">Installation</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>Point-in-time restore of database backup?</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2010/12/28/point-in-time-restore-of-database-backup.aspx</link><pubDate>Tue, 28 Dec 2010 16:42:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:32051</guid><dc:creator>TiborKaraszi</dc:creator><slash:comments>2</slash:comments><comments>http://sqlblog.com/blogs/tibor_karaszi/comments/32051.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/tibor_karaszi/commentrss.aspx?PostID=32051</wfw:commentRss><description>SQL Server 2005 added the STOPAT option for the RESTORE DATABASE command. This sounds great - we can stop at some point in time during the database backup process was running! Or? No, we can't. Here follows some tech stuff why not, and then what the option...(&lt;a href="http://sqlblog.com/blogs/tibor_karaszi/archive/2010/12/28/point-in-time-restore-of-database-backup.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=32051" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Backup/default.aspx">Backup</category><category domain="http://sqlblog.com/blogs/tibor_karaszi/archive/tags/Transaction+log/default.aspx">Transaction log</category></item></channel></rss>