Enterprise vs Standard

After performing an Audit we discovered that my
predicessor inadvertantly installed a SQL 2000 Enterprise
Edition instead of Standard.
This weekend I will be upgrading to a new Server and wish
to use this window to convert to the proper version of
SQL 2000.
It is my understanding that you can upgrade Standard to
Enterprise but cannot perform the reverse.
My question is, are the System databases the same between
versions.
I realize that master.spt_server_info.attribute_id Value
2 would need to be changed (DBMS_VER) as well as
attribute 500 (SYS_SPROC_VERSION)
Other than that does any body know why I cannot do the
following.
1. Backup all Databases on Original Server.
2. Modify the DBMS_VER. and SYS_SPROC_VERSION.
2. Stop All SQL Services on Original Services.
3. Copy All mdf and ldf to a network storage local.
4. Shut down the Original Server.
5. Remove the Original Server from Active Directory.
6. Boot up the New Server with the original IP Address
and Computer name.
7. Install SQL 2000 Standard.
8. Install SP 3a.
9. Stop All SQL Services.
10. Copy all mdfs and ldfs from the network storage to
the proper folder on the new Server.
11. Restart the SQL services.
Does anyone see any major problems with this?
I know I could just attach the the Database but then I
would have to re-write all jobs and create all users in
the master DB providing the SID and Password. SID are not
a problem, but some of the Passwords may be difficult to
come by. (Damn my predisesor!).Your scheme should work, from an architectural standpoint. And it most
probably will. But it is not supported, so give yourself time to verify that
everything seems OK after the switch. You need to make sure that you have
the same directory structure for the SQL Server database files.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"A Dubey" <adubey@.winstead.com> wrote in message
news:de1d01c40ae6$121701b0$a101280a@.phx.gbl...
> After performing an Audit we discovered that my
> predicessor inadvertantly installed a SQL 2000 Enterprise
> Edition instead of Standard.
> This weekend I will be upgrading to a new Server and wish
> to use this window to convert to the proper version of
> SQL 2000.
> It is my understanding that you can upgrade Standard to
> Enterprise but cannot perform the reverse.
> My question is, are the System databases the same between
> versions.
> I realize that master.spt_server_info.attribute_id Value
> 2 would need to be changed (DBMS_VER) as well as
> attribute 500 (SYS_SPROC_VERSION)
> Other than that does any body know why I cannot do the
> following.
> 1. Backup all Databases on Original Server.
> 2. Modify the DBMS_VER. and SYS_SPROC_VERSION.
> 2. Stop All SQL Services on Original Services.
> 3. Copy All mdf and ldf to a network storage local.
> 4. Shut down the Original Server.
> 5. Remove the Original Server from Active Directory.
> 6. Boot up the New Server with the original IP Address
> and Computer name.
> 7. Install SQL 2000 Standard.
> 8. Install SP 3a.
> 9. Stop All SQL Services.
> 10. Copy all mdfs and ldfs from the network storage to
> the proper folder on the new Server.
> 11. Restart the SQL services.
> Does anyone see any major problems with this?
> I know I could just attach the the Database but then I
> would have to re-write all jobs and create all users in
> the master DB providing the SID and Password. SID are not
> a problem, but some of the Passwords may be difficult to
> come by. (Damn my predisesor!).|||Thanks,
I felt like it would, Just wanted to get a little feed
back incase I was missing something.
AD
>--Original Message--
>Your scheme should work, from an architectural
standpoint. And it most
>probably will. But it is not supported, so give yourself
time to verify that
>everything seems OK after the switch. You need to make
sure that you have
>the same directory structure for the SQL Server database
files.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"A Dubey" <adubey@.winstead.com> wrote in message
>news:de1d01c40ae6$121701b0$a101280a@.phx.gbl...
Enterprise
wish
between
Value
not
to
>
>.
>