﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Greg Robidoux / Article Discussions / Article Discussions by Author  / SQL Server Upgrade Recommendations and Best Practices Part 1 / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 20:48:18 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: SQL Server Upgrade Recommendations and Best Practices Part 1</title><link>http://www.sqlservercentral.com/Forums/Topic10312-103-1.aspx</link><description>&lt;P&gt;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:&lt;/P&gt;&lt;P&gt;convert(money(2), somevalue) &lt;/P&gt;&lt;P&gt;This throws an error in SQL 2000 because, well convert changed from 7 to 2k. The statement works fine on 2000 this way:&lt;/P&gt;&lt;P&gt;convert(money, somevalue)&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description><pubDate>Wed, 03 Mar 2004 10:28:00 GMT</pubDate><dc:creator>psullivan</dc:creator></item><item><title>RE: SQL Server Upgrade Recommendations and Best Practices Part 1</title><link>http://www.sqlservercentral.com/Forums/Topic10312-103-1.aspx</link><description>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! </description><pubDate>Tue, 15 Apr 2003 07:15:00 GMT</pubDate><dc:creator>jeremyk</dc:creator></item><item><title>RE: SQL Server Upgrade Recommendations and Best Practices Part 1</title><link>http://www.sqlservercentral.com/Forums/Topic10312-103-1.aspx</link><description>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.Andyhttp://www.sqlservercentral.com/columnists/awarren/</description><pubDate>Tue, 15 Apr 2003 06:01:00 GMT</pubDate><dc:creator>Andy Warren</dc:creator></item><item><title>RE: SQL Server Upgrade Recommendations and Best Practices Part 1</title><link>http://www.sqlservercentral.com/Forums/Topic10312-103-1.aspx</link><description>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 </description><pubDate>Tue, 15 Apr 2003 01:52:00 GMT</pubDate><dc:creator>mhoac</dc:creator></item><item><title>SQL Server Upgrade Recommendations and Best Practices Part 1</title><link>http://www.sqlservercentral.com/Forums/Topic10312-103-1.aspx</link><description>Comments posted to this topic are about the content posted at &lt;A HREF=http://www.sqlservercentral.com/columnists/GRobidoux/sqlserverupgrade.asp&gt;http://www.sqlservercentral.com/columnists/GRobidoux/sqlserverupgrade.asp&lt;/A&gt;</description><pubDate>Sun, 02 Mar 2003 00:00:00 GMT</pubDate><dc:creator>grobido</dc:creator></item></channel></rss>