Thursday, November 30, 2006

Upgrade Madness

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.


Anonymous said...

I guess it's a balance between not letting you install code w/ missing dependancies(it would have thrown an object does not exist error),or not letting you install code w/ missing dependancies causing you to install related objects in the exact order you would need to in order to keep dependancies in line.(installing a table that a sproc accesses before installing the sproc) I guess it's a matter of preference, but It would be nice to have an option allowing you to set it either way.

About Me

My Photo
Sean McCown
I am a Contributing Editor for InfoWorld Magazine, and a frequent contributor to as well as I live with my wife and 3 kids, and have practiced and taught Kenpo for 22yrs now.
View my complete profile


Blogumulus by Roy Tanck and Amanda Fazani

Page Views