Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server Upgrade Recommendations and Best Practices Part 1 Expand / Collapse
Author
Message
Posted Sunday, March 02, 2003 12:00 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, August 05, 2013 7:38 AM
Points: 20, Visits: 174
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/GRobidoux/sqlserverupgrade.asp


Greg Robidoux
Edgewood Solutions
www.edgewoodsolutions.com
Post #10312
Posted Tuesday, April 15, 2003 1:52 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, May 08, 2007 12:12 AM
Points: 12, Visits: 1
Thanks for the excellent article. One thing I do miss, as with other upgrade resoruces/articles I have read so far, is that the upgrade is entirely focused on the server upgrade. There is not much mentioned about the client upgrade process.

BR /Minh




Post #55271
Posted Tuesday, April 15, 2003 6:01 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: 2 days ago @ 9:01 AM
Points: 6,705, Visits: 1,680
In most cases there are only two things to worry about. If you've changed the server name, you have to either recompile all your apps, change all the DSN/UDL's being used, or put an alias in DNS (by far the easiest). Other than that, if you're now using a named instance you may need to upgrade the MDAC on the clients. Other than that, clients should run exactly as before.

Andy
http://www.sqlservercentral.com/columnists/awarren/




Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #55272
Posted Tuesday, April 15, 2003 7:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 06, 2007 4:24 AM
Points: 5, Visits: 1
Mhoac and Andy - Thank you both for the valuable feedback. Since this is a series of upgrade articles, I will include the client portion of the upgrade in a future article. Stay tuned!




Post #55273
Posted Wednesday, March 03, 2004 10:28 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, April 01, 2014 9:57 AM
Points: 56, Visits: 13

I love the article, straight forward, etc. I've read a few upgrade articles recently because a client is upgrading from SQL 7 to SQL 2000. I've been running their database on my local server to see if there are any issues in the upgrade, and found exactly 1 (so far). It involves differeneces in SQL. They are using a lot of statements such as this:

convert(money(2), somevalue)

This throws an error in SQL 2000 because, well convert changed from 7 to 2k. The statement works fine on 2000 this way:

convert(money, somevalue)

So far I've had a hard time find information on similar problems in upgrading from 7 to 2000. If I were doing a 6.5 upgrade I would have that handy tool microsoft issues which helps find some of these kinds of problems. Too bad it doesn't work with 7.0 databases.




Post #103966
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse