SQL Server 2005 ruins SQL Server 2000 ?

[daveroam]

Hi,

On the weekend I installed SQL Server 2005 trial edition on my Db machine. Then I read somewhere that I should not open my existing SQL Server 2000 databases using it as it would irretrievably 'upgrade' them. I think usual M$ force upgrade trickery. There was no warning during the SQL Server 2005 install about this, but to play safe I backed up my existing Dbs from SQL Server 2000 EM and uninstalled SQL Server 2005. This left the console plugin for EM missing for SQL Server 2000. So I ran SQL Server 2000 SP4 again, at least now EM works, but the database is no longer valid!!!!

Any way to reattached to my data and log files without a fresh install of SQL Server 2000? Even if I do, has the SQL Server 2005 altered them to make them unreadable by SQL Server 2000?

Thx.

David

 

[ptheriault]

Do you have a backup of your databases prior to the install of 2005? I would start by restoring them. You can use the 2k5 tools if you want. They have no impact on the database.

- Paul
- Database performance looks fine, it must be the Network!

 

[daveroam]

Hi,

I cannot restore. In EM SQL Server Group I have no database, when I add my original database I get an error. "SQL Server does not exist or access denied ConnectionOpen\Connect()". This occured when I uninstalled SQL Server 2005.

David

 

[daveroam]

Stupid me. For some reason when I restarted the server SQL Server did not start, this was immediately after uninstalling SQL Server 2005. Not sure why the status of the NT Service would be altered but there you go.

Thx.

David

 

[ptheriault]

Was this a named instance or default? You may have to reinstall the instance. Can you see any referrence to the instance in the registry.
HKEY_LOCAL_MACHINE -> Software -> Microsoft -> Mircosoft SQL Server.

- Paul
- Database performance looks fine, it must be the Network!

 

[mrdenny]

If you install SQL 2005 on a machine that already has SQL 2000 installed, SQL 2005 want's to do an upgrade.

You should never install software on your production machine until after you have done it on a test machine first.

I currently use the SQL 2005 GUI to manage all my SQL 2000 servers with no problems. Microsoft doesn't do any sort of upgrade trickery. If they did, they wouldn't get paid for the upgrades.

If you install SQL 2005 side by side on a machine with SQL 2000 you have to reinstall SQL 2000 Service Pack 4 to fix several problems with the SQL 2000 Enterprise Manager.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com