August 12, 2009 at 11:08 am
I haven't been able to find any real good documentation on this so I figured I would post here. Does anyone know if there would be a conflict with having 2005 and 2008 on different clustered nodes?
current environment (3 clustered node active/passive)
Server A. SQL 2005 failover to Cluster C
Server B. SQL 2008 Install Failover to either A or C
______________________________________________
I performed the installation of 2008 , didn't run into any issues during the installation, however after post install in noticed in Cluster Admin
that the resources for the SQL Server network name/Server service/SQL Agents were all offline and or failed to come online even though the sql server service was running (noticed this under sql config manager)
_______________________________________________
The event view did show an interesting message stating the following.
The computer account for Cluster resource 'SQL Network Name (CO-DI-SH01-D03)' in domain admin.cps.k12.il.us could not be created for the following reason: Unable to create computer account.
The text for the associated error code is: Access is denied.
The Cluster Service Account may lack the proper access rights to Active Directory. The domain administrator should be contacted to assist with resolving this issue.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
_________________________
Our infrastructure team is looking into this part for us, but I wanted to be pro-active to see if there was an issue with having the two platforms running. I dont' see it being an issue as they are both running on different instances and binaries are in separate locations etc. any thoughts would be appreciated.
August 17, 2009 at 10:14 am
Found this, hope it helps...
Yes, mixed version clusters are supported in SQL Server.
Installing SQL 2008 is different from SQL 2005. Read up on the new
procedures. They are much easier. You will like them a lot better than the
SQL 2005 installer.
Follow the rules for installing a second instance and you will be fine. You
will need a new disk, IP address, and network name for the new instance.
--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP
Oraculum
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply