<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Developer hearted / Relational minded : T-SQL</title><link>http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx</link><description>Tags: T-SQL</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Cannot find the source of a SQL Server error ?</title><link>http://blogs.msdn.com/jenss/archive/2009/09/25/cannot-find-the-source-of-a-sql-server-error.aspx</link><pubDate>Fri, 25 Sep 2009 11:33:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9899392</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9899392.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9899392</wfw:commentRss><description>Ever had an error in your application and you couldn't find the source of all evil and where the error is thrown at the end ? Well, SQL Server profiler does a great job about that, but you really need to understand which events to filter for and how to...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/09/25/cannot-find-the-source-of-a-sql-server-error.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9899392" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx">SQL Server 2000</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://blogs.msdn.com/jenss/archive/tags/Profiler/default.aspx">Profiler</category></item><item><title>Database Programming: Did You Know IN Can Do This?</title><link>http://blogs.msdn.com/jenss/archive/2009/09/06/database-programming-did-you-know-in-can-do-this.aspx</link><pubDate>Sun, 06 Sep 2009 19:50:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9891972</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9891972.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9891972</wfw:commentRss><description>Ward Pond , one of the marvelous SQL geeks within Microsoft published a nice thing wich we had a discussion internally on concerning the capabilities of the IN operator: http://blogs.technet.com/wardpond/archive/2009/09/04/database-programming-did-you-know-in-can-do-this.aspx...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/09/06/database-programming-did-you-know-in-can-do-this.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9891972" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category></item><item><title>Light weight SQL Server procedure auditing without using SQL Server auditing</title><link>http://blogs.msdn.com/jenss/archive/2009/06/08/light-weight-sql-server-procedure-auditing-without-using-sql-server-auditing.aspx</link><pubDate>Mon, 08 Jun 2009 22:50:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9709243</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9709243.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9709243</wfw:commentRss><description>A week ago a colleague asked for different options to do audit stored procedure calls. With his allowance I will post the question here. “The applications used at the customer site all access these databases using stored procedures ( only , as far as...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/06/08/light-weight-sql-server-procedure-auditing-without-using-sql-server-auditing.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9709243" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/jenss/attachment/9709243.ashx" length="5072" type="application/x-zip-compressed" /><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx">SQL Server 2000</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category></item><item><title>The “magic” about trustable relationships with NULL and NOT IN</title><link>http://blogs.msdn.com/jenss/archive/2009/05/25/the-magic-about-trustable-relationships-with-null-and-not-in.aspx</link><pubDate>Mon, 25 May 2009 22:52:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9640794</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9640794.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9640794</wfw:commentRss><description>&amp;#160; As a follow-up to my former post “ Why you shouldn't´trust the friendship of NULL and the (NOT) IN predicate ” I asked Paul Randal during our SQL Server Master training about the possible internal reason that the results can vary if you have NULL...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/05/25/the-magic-about-trustable-relationships-with-null-and-not-in.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9640794" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx">SQL Server 2000</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category></item><item><title>A long (but not missed) friend revisited, prefixing stored procedures with SP_</title><link>http://blogs.msdn.com/jenss/archive/2009/04/28/a-long-but-not-missed-friend-revisited-prefixing-stored-procedures-with-sp.aspx</link><pubDate>Tue, 28 Apr 2009 09:59:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9573121</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9573121.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9573121</wfw:commentRss><description>Coming as a simple sample with PBM (creating a policy with a condition that procedure names shouldn't´t start with SP_) and getting an interesting question in one of my classes, I wanted to revisit the question about the yet in some places existing naming...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/04/28/a-long-but-not-missed-friend-revisited-prefixing-stored-procedures-with-sp.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9573121" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx">SQL Server 2000</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://blogs.msdn.com/jenss/archive/tags/Performance/default.aspx">Performance</category></item><item><title>When is random “random enough” ?</title><link>http://blogs.msdn.com/jenss/archive/2009/04/08/when-is-random-random-enough.aspx</link><pubDate>Wed, 08 Apr 2009 10:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9537534</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9537534.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9537534</wfw:commentRss><description>An interesting question came up in a private conversation. If you want to pick a random value from a random generated result set and want to make sure that the row is really random, is the known ORDER BY NEWID() really random enough ? The point is that...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/04/08/when-is-random-random-enough.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9537534" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://blogs.msdn.com/jenss/archive/tags/ADO.NET/default.aspx">ADO.NET</category></item><item><title>Why you shouldn't´trust the friendship of NULL and the (NOT) IN predicate</title><link>http://blogs.msdn.com/jenss/archive/2009/03/07/why-you-shouldn-t-trust-the-friendship-of-null-and-the-not-in-predicate.aspx</link><pubDate>Sat, 07 Mar 2009 10:33:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9464006</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>7</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9464006.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9464006</wfw:commentRss><description>A colleague had a problem concerning a query using the (NOT) IN predicate, use the following table creation script (attached to the blog entry) to see the effects of the problem and to repro it on your machine. Imagine you have two tables (not that hard...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/03/07/why-you-shouldn-t-trust-the-friendship-of-null-and-the-not-in-predicate.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9464006" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/jenss/attachment/9464006.ashx" length="3127" type="application/octet-stream" /><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx">SQL Server 2000</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category></item><item><title>Determine the current status of a SQL Server Agent job</title><link>http://blogs.msdn.com/jenss/archive/2009/01/08/determine-the-current-status-of-a-sql-server-agent-job.aspx</link><pubDate>Fri, 09 Jan 2009 00:36:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9300607</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9300607.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9300607</wfw:commentRss><description>Due to the problem that there is no definite table for getting information about the current status of jobs, I created a small procedure grabbing the information from parts of the internal procedures used to extract the very relevant information. As an...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/01/08/determine-the-current-status-of-a-sql-server-agent-job.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9300607" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/jenss/attachment/9300607.ashx" length="2425" type="application/octet-stream" /><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx">SQL Server 2000</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+Agent/default.aspx">SQL Server Agent</category></item><item><title>Tedious trigger generation getting simplified</title><link>http://blogs.msdn.com/jenss/archive/2009/01/08/tedious-trigger-generation-getting-simplified.aspx</link><pubDate>Thu, 08 Jan 2009 14:50:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9296822</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/jenss/comments/9296822.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=9296822</wfw:commentRss><description>While talking with a former colleague of mine, we were elaborating about methods for syncing databases in his company. After boiling down the scenario to a point where we excluded all sync technologies possible, we came down to good old triggers. As of...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/01/08/tedious-trigger-generation-getting-simplified.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9296822" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/jenss/attachment/9296822.ashx" length="5234" type="application/x-zip-compressed" /><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx">SQL Server 2000</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category></item><item><title>Merge it your own way -- Followup on the test</title><link>http://blogs.msdn.com/jenss/archive/2008/07/29/merge-it-your-own-way-followup-on-the-test.aspx</link><pubDate>Tue, 29 Jul 2008 04:04:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8786526</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/jenss/comments/8786526.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=8786526</wfw:commentRss><description>&amp;#160; After publishing the first test results on a previous post I got in contact with the product team to followup the test results. After redoing the test on real hardware and in a client - server scenario, the following result could be extracted from...(&lt;a href="http://blogs.msdn.com/jenss/archive/2008/07/29/merge-it-your-own-way-followup-on-the-test.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8786526" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/Merge/default.aspx">Merge</category><category domain="http://blogs.msdn.com/jenss/archive/tags/Table+Valued+parametersSQL+Server+2008/default.aspx">Table Valued parametersSQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category></item><item><title>Get all system databases of a server</title><link>http://blogs.msdn.com/jenss/archive/2008/07/16/get-all-system-databases-of-a-server.aspx</link><pubDate>Wed, 16 Jul 2008 13:06:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8738139</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/jenss/comments/8738139.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=8738139</wfw:commentRss><description>The easiest way for querying all system databases of a server is to assume that databases create by a user come with a database_id &amp;gt;= 5 in sys.databases. But the problem is that distribution databsaes will not be kept into this consideration. Therefore...(&lt;a href="http://blogs.msdn.com/jenss/archive/2008/07/16/get-all-system-databases-of-a-server.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8738139" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SMO/default.aspx">SMO</category></item><item><title>Obfuscation is not a security feature – Spoofing the APP_NAME</title><link>http://blogs.msdn.com/jenss/archive/2008/05/06/obfuscation-is-not-a-security-feature-spoofing-the-app-name.aspx</link><pubDate>Tue, 06 May 2008 11:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8462463</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/jenss/comments/8462463.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=8462463</wfw:commentRss><description>SQL Server 2005 introduced an interesting and long demanded feature, the LOGON triggers. First only defined via server event triggers, it has become more and more popular in same scenarios to prevent users with a certain machine environment accessing...(&lt;a href="http://blogs.msdn.com/jenss/archive/2008/05/06/obfuscation-is-not-a-security-feature-spoofing-the-app-name.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8462463" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/Custom+Security/default.aspx">Custom Security</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://blogs.msdn.com/jenss/archive/tags/.Net/default.aspx">.Net</category></item><item><title>Merge it your own way - Comparison of SQLAdapter vs. SQLCommand vs. MERGE</title><link>http://blogs.msdn.com/jenss/archive/2008/05/04/merge-it-your-own-way-comparison-of-sqladapter-vs-sqlcommand-vs-merge.aspx</link><pubDate>Sun, 04 May 2008 10:14:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8457820</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/jenss/comments/8457820.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=8457820</wfw:commentRss><description>The question which always comes up in my sessions about SQL Server 2008 is according to my most loved feature in SQL Server 2008, the MERGE command. People always ask me how the performance comparison with MERGE is compared to some standard / traditional...(&lt;a href="http://blogs.msdn.com/jenss/archive/2008/05/04/merge-it-your-own-way-comparison-of-sqladapter-vs-sqlcommand-vs-merge.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8457820" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/Merge/default.aspx">Merge</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category></item></channel></rss>