<?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>Eric Johnson : T-SQL</title><link>http://sqlblog.com/blogs/eric_johnson/archive/tags/T-SQL/default.aspx</link><description>Tags: T-SQL</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>TSQL TRY…CATCH</title><link>http://sqlblog.com/blogs/eric_johnson/archive/2010/10/12/tsql-try-catch.aspx</link><pubDate>Tue, 12 Oct 2010 17:46:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:29095</guid><dc:creator>ejohnson2010</dc:creator><slash:comments>3</slash:comments><comments>http://sqlblog.com/blogs/eric_johnson/comments/29095.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/eric_johnson/commentrss.aspx?PostID=29095</wfw:commentRss><description>Transact-SQL is a great language for data manipulation, but it has its weaknesses. Unlike “real programming languages” T-SQL is confined to procedural code. Sure, you can build “modules” by using stored procedures and functions, but for the most part,...(&lt;a href="http://sqlblog.com/blogs/eric_johnson/archive/2010/10/12/tsql-try-catch.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=29095" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/Error+Handling/default.aspx">Error Handling</category></item><item><title>New T-SQL Functionality in SQL Server 2008</title><link>http://sqlblog.com/blogs/eric_johnson/archive/2010/03/15/new-t-sql-functionality-in-sql-server-2008.aspx</link><pubDate>Mon, 15 Mar 2010 15:00:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:22704</guid><dc:creator>ejohnson2010</dc:creator><slash:comments>2</slash:comments><comments>http://sqlblog.com/blogs/eric_johnson/comments/22704.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/eric_johnson/commentrss.aspx?PostID=22704</wfw:commentRss><description>In my most recent posts I have looked at a few of the new features offered in T-SQL in SQL Server 2008. In this post, I want to take a closer look at some of the smaller additions, but additions that are likely to pack a big punch in terms of efficiency....(&lt;a href="http://sqlblog.com/blogs/eric_johnson/archive/2010/03/15/new-t-sql-functionality-in-sql-server-2008.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=22704" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/INSERT/default.aspx">INSERT</category></item><item><title>SQL Server 2008's MERGE Statement</title><link>http://sqlblog.com/blogs/eric_johnson/archive/2010/03/04/sql-server-2008-s-merge-statement.aspx</link><pubDate>Thu, 04 Mar 2010 16:00:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:22702</guid><dc:creator>ejohnson2010</dc:creator><slash:comments>2</slash:comments><comments>http://sqlblog.com/blogs/eric_johnson/comments/22702.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/eric_johnson/commentrss.aspx?PostID=22702</wfw:commentRss><description>SQL Server 2008 provided us with some new T-SQL syntax; one of those that I am most excited about is the new MERGE statement. Gone are the days of IF....THEN logic to decide whether a row needs to be inserted, updated, or deleted. The MERGE allows you...(&lt;a href="http://sqlblog.com/blogs/eric_johnson/archive/2010/03/04/sql-server-2008-s-merge-statement.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=22702" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/T-SQL/default.aspx">T-SQL</category></item><item><title>Using SQL Server 2008's EXCEPT and INTERSECT Statements</title><link>http://sqlblog.com/blogs/eric_johnson/archive/2010/03/01/using-sql-server-2008-s-except-and-intersect-statements.aspx</link><pubDate>Mon, 01 Mar 2010 21:29:06 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:22701</guid><dc:creator>ejohnson2010</dc:creator><slash:comments>5</slash:comments><comments>http://sqlblog.com/blogs/eric_johnson/comments/22701.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/eric_johnson/commentrss.aspx?PostID=22701</wfw:commentRss><description>SQL Server 2008 shipped with several enhancements to the T-SQL language. In a recent blog, we looked at the new MERGE syntax; today we are going to look at the new EXCEPT and INTERSECT syntax. Both of these operators allow you to compare results of two...(&lt;a href="http://sqlblog.com/blogs/eric_johnson/archive/2010/03/01/using-sql-server-2008-s-except-and-intersect-statements.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=22701" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://sqlblog.com/blogs/eric_johnson/archive/tags/T-SQL/default.aspx">T-SQL</category></item></channel></rss>