﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / T-SQL (SS2K8)  / Data type precedency ntext and hierarchyid / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Mon, 20 May 2013 06:02:16 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Data type precedency ntext and hierarchyid</title><link>http://www.sqlservercentral.com/Forums/Topic1400118-392-1.aspx</link><description>I probably won't be converting to or from HierarchyId. I'm just curious. If someone wants to answer this thread for the theoretical fun, please do.</description><pubDate>Sat, 29 Dec 2012 11:48:03 GMT</pubDate><dc:creator>Golfer22</dc:creator></item><item><title>RE: Data type precedency ntext and hierarchyid</title><link>http://www.sqlservercentral.com/Forums/Topic1400118-392-1.aspx</link><description>[quote][b]Golfer22 (12/25/2012)[/b][hr]Tinyint and bit have a higher precedence than ntext.  Why is this?  Couldn't ntext we complex alphanumeric values?  Tinyint and bit are limited and simple.What precedence does hieararchyid data type have?  I looked here but didn't see anything:  http://msdn.microsoft.com/en-us/library/ms190309.aspx[/quote]You kind of have 2 or 3 questions here.Why is tinyint a higher precedence than ntext? First of all ntext is deprecated so you shouldn't be using it at all. Your argument of it could be complex alphanumeric values is exactly why it fall on the precedence list where it is. You can't do math on alphanumeric values. They have to be numeric to perform calculations. The more relevant reason is that you have crossed the line from something that can be used in a mathematical equation to something that can't (well maybe it can IF the data can be converted). Your second question is about the precedence of HierarchyID. My question would be, does it really matter? Are you going to be implicitly converting to/from the hierarchyID datatype?</description><pubDate>Wed, 26 Dec 2012 08:11:30 GMT</pubDate><dc:creator>Sean Lange</dc:creator></item><item><title>Data type precedency ntext and hierarchyid</title><link>http://www.sqlservercentral.com/Forums/Topic1400118-392-1.aspx</link><description>Tinyint and bit have a higher precedence than ntext.  Why is this?  Couldn't ntext we complex alphanumeric values?  Tinyint and bit are limited and simple.What precedence does hieararchyid data type have?  I looked here but didn't see anything:  http://msdn.microsoft.com/en-us/library/ms190309.aspx</description><pubDate>Tue, 25 Dec 2012 19:08:58 GMT</pubDate><dc:creator>Golfer22</dc:creator></item></channel></rss>