943,958 Members | Top Members by Rank

Ad:
  • MS SQL Discussion Thread
  • Unsolved
  • Views: 5897
  • MS SQL RSS
Jan 12th, 2007
0

SQL 2005 upgrade questions

Expand Post »
We are considering upgrading SQL 2000 to SQL 2005. I just love the idea of getting newer technology, But i'm hesitant to upgrade MS stuff, cause of bugs and licensing stuff... So here's what i'm wondering:

1. If we move to 2005, will we lose any databases/querys/dts packages/etc ?? or is it a seamless upgrade from 2000?

2. Would we have to uninstall 2000 and then install 2005, or is it an in-place-upgrade type of thing?

3. Does 2005 have a forced on-line registration that you have to go through (sort of like how XP has to be "activated")?

4. If we use SQL 2005, and end up using more connections that we purchased, will SQL fail or give an error message? SQL 2000 does not give this problem.
Similar Threads
Reputation Points: 10
Solved Threads: 0
Newbie Poster
simpleton is offline Offline
14 posts
since Jan 2007
Jan 12th, 2007
0

Re: SQL 2005 upgrade questions

Click to Expand / Collapse  Quote originally posted by simpleton ...
We are considering upgrading SQL 2000 to SQL 2005. I just love the idea of getting newer technology, But i'm hesitant to upgrade MS stuff, cause of bugs and licensing stuff... So here's what i'm wondering:

1. If we move to 2005, will we lose any databases/querys/dts packages/etc ?? or is it a seamless upgrade from 2000?

2. Would we have to uninstall 2000 and then install 2005, or is it an in-place-upgrade type of thing?

3. Does 2005 have a forced on-line registration that you have to go through (sort of like how XP has to be "activated")?

4. If we use SQL 2005, and end up using more connections that we purchased, will SQL fail or give an error message? SQL 2000 does not give this problem.
1. You won't lose anything -- you can import the old into the new as legacy DTS packages. SQL Server 2005 comes with SSIS, which is a little more complex than DTS, but definitely better!

3. No, it does not. There are many invitations to provide feedback, but none are required. Various pieces of the suite *will* try to contact crl.microsoft.com to verify that the .Net software's license (?) wasn't revoked, but that doesn't do any type of SQL registration or anything. You may just use the hosts file to block crl.microsoft.com.

4. I really don't think so, but I'm not sure. Nowhere in the software do you actually put how many CALs you have. Of course, you should always have properly licensing!
MCP
Reputation Points: 14
Solved Threads: 3
Light Poster
MCP is offline Offline
44 posts
since Sep 2006
Jan 12th, 2007
0

Re: SQL 2005 upgrade questions

1) I am in the process of doing this right now and so far it has been relatively painless. There are some minor tweaks you may have to make, but it is pretty easy to convert. Two problems we have had is that we couldn't import the master database, so had to recreate users and permissions. All the other databases imported fine. Second was that we had 2 stored procedures (out of more than a hundred) that did not work and had to be rewritten. I believe it was the syntax of using *= for joins so it was a minor change. We didn't try an upgrade in place so I don't know anything about that, we installed 2005 on a brand new box and importing the databases and such.
Reputation Points: 14
Solved Threads: 19
Posting Pro in Training
campkev is offline Offline
484 posts
since Jul 2005

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.
Message:
Previous Thread in MS SQL Forum Timeline: max value
Next Thread in MS SQL Forum Timeline: Howto | mssql seach and replace?





About Us | Contact Us | Advertise | Acceptable Use Policy
Forum Index | Build Custom RSS Feed


Follow us on Twitter


© 2011 DaniWeb® LLC