Lessons learned from upgrading from SQL 2000 to SQL Server 2005

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

arbert — Fri, 05 May 2006 14:16:55 GMT

Nice document, but again, these are issues that anyone well versed in SQL Server could have saved you HOURS on. Lots of these issues were also around in SQL2000 and also happened when you upgraded SQL7.0 to SQL2000.

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

admin — Sat, 06 May 2006 03:31:35 GMT

Arbert/Brett,

>>Nice document, but again, these are issues that anyone well versed in SQL Server could have saved you HOURS on.

Okay...I see from the link on your posting, that you coincidentally happen to be in the business of selling such "well-versed" knowledge on SQL Server for a living. I'm going to ignore the possibility that your posting was made simply to promote your site, rather than contribute to the discussion.

I will simply point out that if you actually read the article, you would already know that "well versed" people were consulted. No one person had all the answers.

Yes one of these issues (the DTA issue) may have been caused by bugs in earlier versions of SQL...but certainly not "lots" of isssues. Additionally, the DTA issue can still occur even on a brand new 2005 server, if it ran pre SP1 and witnessed a crash. So it's both relevant and important that people are informed about this so they can correct the same issue if it happens to them.

Ian

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

dyodyo — Wed, 10 May 2006 04:26:09 GMT

now i really wonder why most of the sites are hosted on linux using apache web servers

hmmm....

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

tpaulengineer — Thu, 11 May 2006 21:37:25 GMT

Although I agree with Arbert that an expert in SQL is valuable, no one should have to deal with these issues in a new released product. Once again Microsoft releases an unfinished product to market. Same as with Visual Studio 2005.

But WOW!, Mister Ian, thank you! This will be super helpful to us.
Sincerely, I am always thankful to folks like you that take the time to show the world the pain they went to in getting something to work.

One of the things you said that really worries me is...We have a huge 120 gig database, and you said you need tons of memory to do full backups.
I want to ask Microsoft... how much memory will I need to do a backup ? 1billion Megs ?
Geeze MicroSLOTH!
I complain, but I seem to find a way to make complicated web applications, with large databases work on their technology, and I'll probably continue to do so for years to come.
Ian, do you know if there is a way to pay a license upgrade fee to move up from sql 2000?

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

arbert — Sun, 28 May 2006 14:27:58 GMT

Of course I wasn't posting to promote my site. I was just amazed at how much of the posted information has nothing to do with SQL2005...MAXDOP/Hyperthreading, Rebuilding Statistics, DTA, all these "problems" have been around forever. Shouldn't have taken a 10k contract upgrade with MS to figure them out.

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

admin — Thu, 01 Jun 2006 16:09:06 GMT

tpaulengineer,

>>One of the things you said that really worries me is...We have a huge 120 gig database, and you said you need tons of memory to do full backups.
I want to ask Microsoft... how much memory will I need to do a backup ? 1billion Megs ? Geeze MicroSLOTH!

If you want to do the verify, then unfortuantely you do. We're still struggling and fighting with the "workaround" that Microsoft suggested (copying it to a 2nd server and verifying there so the production server doesn't get drained of memory). The problem is that during the copy the same memory loss is happening. So perhaps it's related to the OS...I'm not sure. I'll update this on the blog via another post once we get a good answer on how to deal with this issue.

>>Ian, do you know if there is a way to pay a license upgrade fee to move up from sql 2000?

Yes there is (or was...I'm sure it probably still exists). You can probably check with your software provider to make 100% sure.

Ian

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

admin — Thu, 01 Jun 2006 16:21:46 GMT

Arbert,

>>I was just amazed at how much of the posted information has nothing to do with SQL2005...MAXDOP/Hyperthreading, Rebuilding Statistics, DTA, all these "problems" have been around forever.

Actually..if you had read the above carefully:

1) Rebuilding Statistics is a SQL 2005 upgrade issue.
2) The DTA crashes are a SQL 2005 (pre SP1) issue.
3) MAXDOP/hyperthreading may not be directly 2005 specific, but since it wasn't availabe in processors when 2000 was released, it is relevant to 2005. The title of this blog, after all, is "Lessons learned from upgrading from SQL 2000 to SQL Server 2005".

>>Shouldn't have taken a 10k contract upgrade with MS to figure them out.

Well, you're certainly entitled to your opinion. I'll simply say that no one at MS so far has seemed to have a problem with "attention to detail".

Ian

SQL Server 2005 Database issues 95% resolved

Anonymous — Thu, 16 Nov 2006 17:08:45 GMT

As you've probably already noticed, the database issues are almost completely resolved.&nbsp; For the...

Microsoft » Blog Archives » bug installing SQL Server 2005 Express Edition with

Anonymous — Tue, 28 Aug 2007 05:21:58 GMT

PingBack from http://chaespot.com/mssql/2007/08/28/bug-installing-sql-server-2005-express-edition-with/

Microsoft » Blog Archives » Patches are available for the flaws for SQL

Anonymous — Tue, 18 Sep 2007 13:24:45 GMT

PingBack from http://chaespot.com/mssql/2007/09/18/patches-are-available-for-the-flaws-for-sql-3/

Query running slow in SQL 2005 after migrating from SQL 2000 | keyongtech

Anonymous — Sun, 18 Jan 2009 17:05:25 GMT

PingBack from http://www.keyongtech.com/2540708-query-running-slow-in-sql

Upgrade to SQL 2005 - HIGH CPU - Page 2 | keyongtech

Anonymous — Thu, 22 Jan 2009 01:15:50 GMT

PingBack from http://www.keyongtech.com/2230171-upgrade-to-sql-2005-high/2

Lessons learned from upgrading from SQL 2000 to SQL Server 2005

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

re: Lessons learned from upgrading from SQL 2000 to SQL Server 2005

SQL Server 2005 Database issues 95% resolved

Microsoft &raquo; Blog Archives &raquo; bug installing SQL Server 2005 Express Edition with

Microsoft &raquo; Blog Archives &raquo; Patches are available for the flaws for SQL

Query running slow in SQL 2005 after migrating from SQL 2000 | keyongtech

Upgrade to SQL 2005 - HIGH CPU - Page 2 | keyongtech

Microsoft » Blog Archives » bug installing SQL Server 2005 Express Edition with

Microsoft » Blog Archives » Patches are available for the flaws for SQL