Instead of working, I blog.

We recently ran into a very interesting anomoly here upgrading to Yukon. We have the following query.


Select * from DWStsging.dbo.history

Of course, you all know the 3 part naming convention, so you know that DWStsging is the database name. However, what you may not know is that it's misspelled. The real name is DWStaging, and the one in the query is mistyped.

So what makes this interesting? SQL2K runs it just fine, and has for months, while Yukon spits it back at us. It's these little things that upgrading interesting.

These are the kinds of things I really don't mind though. Sure, it's nice that 2K does what you mean, and not necessarily exactly what you say, I'd rather my DB not make assumptions like that. So if anything, Yukon is forcing us to clean up our code where we didn't even know we had problems.

I just ran across this in an SP and I thought I'd share it with you guys...

Select RegionName from Regions
where RegionName IN ('SC', 'MW', 'NE', 'NC', 'NW')


For some reason, I just love the uselessness of this whole thing.