<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Watch Out Pt 1 - Ensure you utilise appropriate data types and use explicit CAST/CONVERT in queries</title><link>http://blogs.technet.com/b/sqlman/archive/2007/09/22/watch-out-pt-1-ensure-you-utilise-appropriate-data-types-and-use-explicit-cast-convert-in-queries.aspx</link><description>I will use the title of "Watch Out" to write about things I see customers implement "incorrectly" or not according to best practices. 
 During a delivery of the SQL Server 2005 Performance Tuning and Optimisation course one of the attendees showed me</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>