Not surprisingly, SQL Server 2000 seems to do some things differently than did version 7. In general, it seems to be less forgiving of sloppiness, such that queries that probably shouldn't have worked in 7 (but did) no longer work in 2000.
I've found at least three such things:
1) Default sort is different.
2) Concatenating a varchar column that contains a value with a column containing a null now produces a null.
3) I may have some old stored procs held over from 6.5 or something. They checked a bit column for -1. These worked in SQL 7. Even though the column actually contained a 1. They no longer work in 2000.
My question is this: Is there anywhere I can go to find a list of these differences, so I can make preventive changes to my SP's before I move them to 2000? Or do I just have to move them and fix the problems as they occur?I would start with this...
http://msdn.microsoft.com/library/en-us/tsqlref/ts_sp_da-di_5c8c.asp?frame=true|||Thanks! That's just the kind of thing I was looking for.
Friday, March 9, 2012
Migration Problems: 7 to 2000
Labels:
database,
differently,
forgiving,
microsoft,
migration,
mysql,
oracle,
server,
sloppiness,
sql,
surprisingly,
version
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment