Most of the posts here for co-existence of sql 2005 and sql 2000 are for upgrades to 2005 or installing sql 2005 on a box already having sql 2000. This is a bit different..
I have an application installed on sql 2005 sp1, on a default instance, no other instances installed. Because of issues the application is having with sql 2005, the vendor is recommending install of sql 2000 on the same box ('should not have any problems' they say), then script out the user databases in SQL 2005 and back in to the sql 2000 instance.
Has anyone tried this (installing sql 2000 after install of sql 2005) or can point me to an article about it? I've googled around and searched the knowledgebase to no avail.
thx
I have done this several times, and have seen some posts in these groups on the same topic (Where the users have not had a problem). You will need to make sure that you use a different instance name for the sql 2000 database system.
|||Glenn,
Thanks for the reply, I'll test it out. I did search back in this forum, and found a few messages, but with mixed results, i.e. some who said to be sure to install sql 2000 first, implying some issues if done the other way around..see link below.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=122124&SiteID=1
|||One issue I could see arise would be that the file extensions for the tools would be changed to reference sql 2000 applications. But you should be able to move these back. With the binerys these are all installed to seperate directories, the same is with the data files. With SQL 2000 they normally save the bin files to MSSQL\80 and for SQl 2005 MSSQL\90 (From memory). And the data files, SQL 2000 are saved inside a directory MSSQL$<instancename> where sql 2005 are save MSSQL.1 and so on... for example MSSQL.2 would be the second instance. There directory names might be a little different as I am going from memory and have not got them installed here. If I remember i will check and update tonight.
No comments:
Post a Comment