Friday, February 24, 2012

Best Way to Upgrade SQL 2000 to 2005

Hello,

I have a project where I have to upgrade SQL 2000 to 2005. When we are upgrading we are going to move to new server so server name will change. Most of our applications have a hard coded connection string. Applications are developed with Classic ASP, .NET 1.1 and 2.0 as well.

Now the question is what is the best way to do this? Changing all the connection string will be a very painful task as we have many applications.

Can anyone suggest a way where we can achieve this without changing all the connection strings?

Thanks in advance.

Tareq

first go to the folder where the mdf files resides and copy it and detach the database in sql 2000...

go to the folder where the sql 2005 databse exists.. paste the files u copied.. and then reattach the databases to it..

Hope this helps..

Regards,

Karen

|||

How would that help with the servername changes in the connection string?

|||

why dont u move all your connection strings to webconfig so suppose if anything happens to a server and something like this all u got to do... change the setting in the webconfig instead of the whole application.

|||

Ideally that is how it should be done and that is how I do it. But our previous developers did not do so that is the problem. Also Classic ASP does not use web.config. They use include files or hard coded in the code. If all the previous developers did it the right way it would have been a breeze. But unfortunately they did not do it the right way. We have over hundred of applications and hence this problem.

|||

Try the Find/Replace. I dont think there's any other way. While you are doing it manually you might as well spend the time to use one connectionstring throughout and put that in the web.config value.

No comments:

Post a Comment