<?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>Implicit Conversions</title><link>http://blogs.msdn.com/craigfr/archive/2008/06/05/implicit-conversions.aspx</link><description>In my last couple of posts, I wrote about how explicit conversions can lead to errors. In this post, I'm going to take a look at some issues involving implicit conversions. SQL Server adds implicit conversions whenever you mix columns, variables, and/or</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>SQL Server 2005 bug when using LIKE searches</title><link>http://blogs.msdn.com/craigfr/archive/2008/06/05/implicit-conversions.aspx#8731300</link><pubDate>Mon, 14 Jul 2008 13:36:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8731300</guid><dc:creator>Zunanji viri</dc:creator><description>&lt;p&gt;Here&amp;amp;#39;s a demo of a nice little bug in SQL Server 2005 when using LIKE comparisons for searching.&lt;/p&gt;
</description></item></channel></rss>