Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Backporting from 2000 to 7.0

Author  Topic 

Lavos
Posting Yak Master

200 Posts

Posted - 2003-03-10 : 11:32:09
Due to various shady contractors that my company's client used before us, it turns out that the only valid license that the client has is for 7.0 instead of 2000. (The client probably didn't know any better, but yikes)

We're in the process of putting together some different proposals for how to go forward, but an option is to *Shudder* backport the database part of the application.

From what I understand, there are no user defined functions in 7.0, and I know there are no table variables.

What else would I have to look out for while backporting? I'm not using any of the "enterprise" features (confederated servers, indexed views), and haven't had a reason to use "instead of" triggers.

With any luck, it would be cheaper to get the 2000 license instead of paying me to backport the application, but I would like to know any major gotchas before I begin to draft the proposal.

----------------------
"O Theos mou! Echo ten labrida en te mou kephale!"

So Long and Thanks for the Links.

Page47
Master Smack Fu Yak Hacker

2878 Posts

Posted - 2003-03-10 : 11:35:07
DTS is a major difference.

Jay White
{0}
Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2003-03-10 : 11:37:53
Probably the best thing to do is open up BOL 2000 and go to the "What's New?" section. Anything in there may give you some hassles if you have take a step back. Also, sql_variant and bigint datatypes were introduced in SQL 2000, as were non-server level collation settings.

Go to Top of Page

rjpaulsen
Starting Member

9 Posts

Posted - 2003-03-10 : 18:56:15
Try setting the compatability mode from 80 to 70. Although that won't effect DTS packages, it will cover most everything else.

Make a list: 'Features We Use.' Check that list instead of checking a list of all changes. SQL2K has many non-compatable changes (DTS, User Functions, *replication*) -- just focus on the features you use.

Since conversion time will cost money, it would be money best spent to upgrade your License. It doesn't take many programer hours to equal a SQL License.


Go to Top of Page
   

- Advertisement -