SQL Server 2000 Enterprise vs Standard editions 2

[JohnBates]

Hi SQL Servers !

We will be upgrading from ver 7 to 2000 this year.
Trying to determine which version (Enterprise or Standard) we need.

We use merge replication. Both editions can handle replication. Something called Failover Clustering is supported in Enterprise but not in Standard.
I'm not sure what Failover Clustering is.

HTTP Internet Support is another feature (avail only in Enterprise) that I'm not sure about.

Standard does support multiple instances. For purposes of converting my db from ver 7 to 2000... how can I perform the conversion if I want to convert the db to another server machine that is running SQL Server 2000 Standard ?
Or is it better to install 2000 Standard on my existing server (so it would be running multiple instances after that)?

I hope my questions make sense.
Thanks, John

 

[tlbroadbent]

I can't answer questions about Failover clustering or HTTP Internet support because we use only standard edition. You can run multiple instances of Standard Edition on the same server but each edition must be licensed separately. The Enterprise Edition allows running of multiple instances with one license.

If SQL 7 is running on oine server and SQL 2000 on another you can easily convert the SQL 7 databaes to SQL 2000 by

1) restoring a backup from SQL 7 to SQL 2000.
2) detaching the database in SQL 7, moving the database files to the SQL 2000 server and attaching the database in SQL 2000.

Using either methood you'll need to make sure you script SQL 7 logins and add them to SQL 2000. Then you'll have to synchronize database users to the logins on SQL 2000. See FAQ183-2153 for more details on this topic.

I really recommend upgrading SQL 7 to SQL 2000. Let setup upgrade all the databases. Then you don't have to worry about logins, passwords, users, DTS packages, scheduled jobs, etc. Setup handles everything. If you create a new instance, whether on the same server or a different server, you'll have to transfer packages, jobs, logins, etc. It is much easier and cleaner to upgrade. At least that has been my experience through 10 upgrades from SQL 7 to SQl 2000. Terry L. Broadbent - DBA
Computing Links:

http://tlbroadbent.home.attbi.com/prog.htm

faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.

 

[Corran007]

It really depends on how mission critical your database applications are. Failover Clustering allows you to sync up two or more identical databases instances on different machines. they can be configured to run together or to run one as active one as backup. if one goes down, the other kicks in. We will have one set up for our new HR system.

Basically if you are going to have clustered databases, go with enterprise. if not go with standard. Only enterprise level applications need this, hence the name enterprise version. Most applications do not need it. Its really only needed for 100% uptime applications, like our new HR system.

I dont know anything about http internet support.

 

[JohnBates]

Terry and Corran007, thanks for your ideas and opinions.

Terry you said "Let setup upgrade all the databases. Then you don't have to worry about logins, passwords, users, DTS packages, scheduled jobs, etc. Setup handles everything."

I'd like to learn more about the Setup feature. If I install 2000 Standard on a new server... can I use Setup to copy my version 7 database from another server and convert packages, logins, data etc over to the new 2000 server?

Thanks, John

 

[tlbroadbent]

The article at the following link should answer most of your questions.

http://www.microsoft.com/technet/prodtechnol/sql/deploy/upgrdmigrate/sqlugrd.asp

There is also an upgrade FAQ.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q261334

Terry L. Broadbent - DBA
Computing Links:

http://tlbroadbent.home.attbi.com/prog.htm

faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.