Koen Verbeeck (11/9/2011)

---

The MSDN article doesn't specify the precedence of the date datatype

Because values from different data type families must be explicitly cast before being referenced in comparison predicates, the effects of the The values in the following table are examples of the rules regarding data type precedence.

create table #test(id int, val sql_variant)

insert into #test values(1,'2')
insert into #test values(2,1)
insert into #test values(3,3)
insert into #test values(4,0)

select *,sql_variant_property(val,'BaseType') from #test order by val


/* Result */
id	val	(No column name)
1	2	varchar
4	0	int
2	1	int
3	3	int

Hugo Kornelis (11/10/2011)

---

Nice question, Ron!

I only got it right because I figured that the relative order of the date and time related values would be "logical". And since the conversion to smalldatetime would chop off the seconds and the conversion to date the entire time portion, the only logical ordering of those three would be date / smalldatetim / datetime.

Nils Gustav Stråbø (11/10/2011)

---

Good question, but I'm not sure that the explanation is 100% correct.

Because values from different data type families must be explicitly cast before being referenced in comparison predicates, the effects of the something is missing here The values in the following table are examples of the rules regarding data type precedence.