I am trying to remove Analysis Server from a cluster. I have done the research and according to MS you can't use the regular add/remove programs dialog to remove a component. You have to use the setup.exe from the command line.
This article (http://support.microsoft.com/kb/910230) explains at the very bottom to run this command "Start /wait <DiskDrive>setup.exe /qb REMOVE=Analysis_Server INSTANCENAME=<InstanceName>". Well I do that and I get the installer up and running but when it gets to that system configuration check screen, where it runs a bunch of checks on the nodes, it just closes before it does any checks and nothing further happens. I can't find any error in the event log or find any log files on disk related to why its just closing.
Just to investigate further, I wondered what executable was running when you ran the installer though the add/remove programs dialog, so I looked in the registry. Well along with the SQL Server 2005 entry, which runs the setup bootstrap program in your default install folder, I noticed an entry that was idenified only by its GUID. Looking at the sub keys I noticed the DisplayName was Microsoft SQL Server 2005 Analysis Services. The UninstallString key was set to "MsiExec.exe /I{52B0D62A-860D-4136-9A8A-9FD877E8EE89}" so I ran that. The installer seems to work, but it doesnt run any configuration checks. I get to the screen with the big button to change components with no errors. Then it acutally shows Analysis Services installed (the disk icon is not xed out), I can then click and select entire feature will be unavailable. I haven't proceeded on this step because I am worried about the cluster.
I am assuming that this uninstaller will only remove analysis services from the node its running on. This is fine, cause I can just run this same procedure on all the nodes... and then i would assume I would have to manually clean up the cluster resource. But I have not tested this, and unfortuanlly I don't have a development cluster to try this on.
Does anyone have experience with removing Analysis Services from a failover cluster environment?
In case of hardware unrecoverable issue, I have two msdn articles which states different things.
First one claims you remove the node from mscs.
[URL]
Second one claims you should remove it using sql server installation and links to the first link which says you should do it from mscs:
[URL]
Then this third article invalidates the second article. "To remove a node from an existing SQL Server failover cluster, you must run SQL Server Setup on the node that is to be removed from the SQL Server failover cluster instance."Â
[URL]
It is a hardware faillure where the secondary node is inaccessible.
So what is the proper way to evict a node you cannot access due to a hardware failure?
note: I don't plan on adding back the failed nodes after removing it. i.e. I am interested in the removing part.
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
I read on MSDN how to manually uninstall the instance of SQL server 2005 express, however i am not sure that it will remove the service. The reason i need to do this is that an application i have installed SQL Server 2005, and also QPulse5 SQL Server. I have two instances and it is giving me compile issues which i believe is related to having both services. I did add/remove programs and reinstalled just SQL Server 2005 and recieved error message saying that the service failed to start. The whole problem of this occured when we ran DCPromo with SQL installed. After we did we relized you could not promote with SQL Server. I understand that it is not recommended running SQL Server on a DC, however we did not have a choice. I am hoping someone here may have a solution for this. If there is any other information you need just let me know. Thanks
I just removed (via Add and remove programs) SQL 2000 Server and now only have SQL 2005 left on my machine. The 2005 Server (SQLExpress?) is set up for mixed mode and I've verified that the registry setting is 2 for LoginMode, yet I'm still unable to login. This is the following error?
TITLE: Connect to Database Engine ------------------------------
Login failed for user 'drafttrackuser'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
------------------------------ BUTTONS:
OK ------------------------------
Naturally, the link goes no where. I've searhed this site and it seems most of the problems are either more complex (linked servers, clusters etc.) or are people who haven't set the server to work in mixed mode. I've rebooted a couple of times but the errors persist.
Sometimes at the end of a project you'll end up with unused Tables,Stored Procs, Functions, and Views.Since there is not something like a 'SELECT' trigger ... what is thebest way for telling what is not being used by your solution? To turnon some kind of tracing?Any ideas?Thanks,Kelly GreerJoin Bytes!change nospam to yahoo
got problem with uninstallin sql so i ended both sql exe files in Services and Progresses then removed c:program filsmicrosoft sql server manually and some keys about sql in registry
when i reinstall, no problem with SQL setup support files SQL Native Client SQL VVS writer couldnt pass thru the "SQL Server Database Services" Installation
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
SQL Server æœ?åŠ¡æ— æ³•å?¯åŠ¨ã€‚有关详细信æ?¯ï¼Œè¯·å?‚阅 SQL Server è?”机丛书ä¸çš„主题€œå¦‚何查看 SQL Server 2005 安装日志文件€?å’Œ€œæ‰‹åŠ¨å?¯åŠ¨ SQL Server€?。 ( SQL server services fail to start. For more information ... blah blah blah and Start SQL server manually )
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlShutDownRANUInstance%40sqls%3a%3aService%3a%3aStart%40x422
------------------------------ BUTTONS:
&Retry Cancel ------------------------------
when i goto SQL server Configuration Manager, it says:
MMC could not create the snap-in CLSID: {CA9F8727-31DF-41D2-975C-887D84903967}
I was trying an edition upgrade from SQL 2005 standard x64 to SQL 2005 enterprise x64 using the "setup SKUUPGRADE=1" from the command line. The SO is W2003 server R2 enterprise and I have a SQL clustered environment with 2 nodes (active/passive).
I select to upgrade the SQL module and I mark the checkbox for the cluster installation. The installation seems to work properly untill setup is doing the task "removing backup files". Then 2 "unexpected error" message appears as follows. The 2 above windows appear when you click on the help icon.
Link to screen capture
The following is the end of the SQL setup log file:
Apparently you cannot go backwards. Once 2005 Express is installed, even removing it does not allow you to setup MSDE 2000 again. So there is no "trying it out" option.
Unfortunately, our software does not use 2005 Express. I tried it out, and now have a useless testing workstation that can't have MSDE 2000 installed again.
Any ideas on how to break the chain here are welcome.
For the past several weeks, I have been trying to install SQL Server 2005 on a Win XP SP2 PC. Regardless of the options I choose (SQL Engine + Client Tools, Client Tools only, etc.) when the installation gets to the end of the Client Tools setup and the setup status displays "Removing Backup Files", my PC appears to hang.
For a period of time, there is a fair amount of HD activity which gives me the impression that files are in fact being deleted, but then there is no HD activity and the installation appears to hang. Finally I give up and kill the setup process and reboot.
After reboot, it appears that the client tools have been installed (the icons appear and I can open the Management Studio, but when I try to connect to an existing instance of SQL, that hangs. This occurs for either Windows or SQL authentication.
Has anyone experienced this behavior and determined the root cause? What EXACTLY is happening during the "Removing Backup Files" phase of the installation?
I have a virtual machine that previously had SQL Server 2005 installed. Since I changed the computer name, I have to reinstall SQL. I removed all the SQL components and am trying to reinstall the database and reporting components. The installation is failing on the "Removing temporary files" step. According to the setup progress screen, the following components have been installed:
OWC11
SQL Server Bakcward-Compatibility Files
SQL Server Database Services
Reporting Services
Visual Studio Integrated Development
SQL Server Books Online
SQLXML4
Workstation Components, Books Online - this step is still in "configuring components" status.
The virtual machine is running Windows 2003 Server SP1 with all current patches, using just under 2 GB of memory (1920 MB of RAM), the host is Windows XP SP2 with all current patches, with 4 GB of memory.
I had no problem doing this procedure on a different virtual machine, so I'm not sure what the problem is here.
When I run sp1 on the active node of a 64-bit cluster the setup just hangs when it gets to the Database services part. It does not return any errors as mentioned by others in this forum. I also do not have SqlSupport.msi in the add/remove programs (one suggestion on this forum was to uninstall it reinstall). I have let it run for up to 12 hours with no result.
There is no SQL9_Hotfix_KB913090_sqlrun_sql.msp.log file only SQL9_Hotfix_KB913090.log
this is the content
05/09/2006 12:41:12.274 ================================================================================ 05/09/2006 12:41:12.274 Hotfix package launched 05/09/2006 12:41:15.634 Product discovery successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 SP Level check successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 Product language check successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 Product version check successfully completed during the install process for DEV01 05/09/2006 12:41:15.681 Product discovery successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 SP Level check successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 Product language check successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 Product version check successfully completed during the install process for DEV02 05/09/2006 12:41:15.743 Product discovery successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 SP Level check successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 Product language check successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 Product version check successfully completed during the install process for DEV03 05/09/2006 12:41:15.790 Product discovery successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 SP Level check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Product language check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Product version check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Command-line instance name check completed during the install process 05/09/2006 12:41:15.868 Baseline build check completed during the install process 05/09/2006 12:44:25.795 Attempting to install instance: DEV02 05/09/2006 12:44:25.795 Enumerating passive cluster nodes 05/09/2006 12:44:25.873 Patching available passive node: TTCSQL62A 05/09/2006 12:44:25.873 Waiting for first successfully completed passive node 05/09/2006 12:44:25.873 Attempting to patch running passive node: TTCSQL62A
we want to have an activepassive and active passive cluster.
node a install sql instance 1 failover over to node b
node b install sql instance 2 failover to node a
do I have to setup 2 cluster ? ie. quorum, msdtc etc..
or just one cluster(quorum, ip and name), one msdtc group( as per MS msdtc doc) and 2 san disks (one for node a and one for node b.
is this correct? I have looked and looked for a step by step on setting this up, no where can I find what i need. I downloaded the failover cluster doc from microsoft, book online etc..
I want to create an activepassive on both nodes. (onenode will be the active node for on sql install while the other is passive.
I want to repeat this fo rthe second node, the second node being active and node 1 passive.
I logged into node 1 and I installed sql 2005 in failover cluster into sqlinstance 1., everyhting was fine, failover etc.
Now I logged into node 2 and ran sql 2005 setup to create a failover cluster.
I chose to install into sql instance 2.
Database unable to install with error "failed to set registry settings for server network libraries. acition is setdefaults.error 11001, no such host is known.
If I am not setting this up correclty please let me know
thanks
everything was fine. I logged onto node 2, was going to
I'm having trouble finding the recommended process for doing a full Disaster Recovery on a two node active/passive sql 2005 cluster. I've been able to locate the procedure for rebuilding a failed node on the msdn site but no procedure for recovering the entire system. Any assistance or points in the right direction are appreciated.
I have just recently inherited a sql server 2005 cluster (2 nodes) we have a situation coming up where i need to power down the whole cluster for several hours as a result of some power mains work.
I just need to confirm with someone the correct way to power down the whole cluster and power it back up once the power is restored the company. I appreciate this may not be the best place to have posted this but i am desperate and couldn't find another location.
Anyone know before I invest in the hardware if it is possible to have Two Clusters on the same hardware both in Active/Passive Clustering where Cluster1 and Cluster2 both use the Default SQL Server 2005 Instance (No Named Instances)?
This would be a Virtual Cluster with Two separate 2 node Clusters on the Same Hardware sharing the same OS and SQL.
I have YET to have a 100% CLEAN install of SQL 2005 in a clustered environment. SQL 2005 Std. was not so bad, I think I finally managed a 99% clean install (no script errors on patches) on the third try.
SQL 2005 EE keeps erroring off on 2153 patch install. The error logs are no help at all; they simply stop logging activity at about the point that the error occurs.
Process: Install OS Patch OS to SP1 Cluster OS on SAN Configure Cluster Groups (DBC01, DBC02, DBC03) with cluster disks Configure MSDTC (network access, configure cluster resources)
Start SQL Installation Install RTM Binaries on Node 1 for Default Instance Install Workstation and non-cluster components on remaining nodes Install RTM Binaries on Node 2 for Named Instance
Reboot all nodes
Install SP1 for all instances from node 1
Install SP1 for all local services/applications for all other nodes
While attempting to install the 2153 SQL patch/hotfix, the process will either: Hang while waiting for the first passive node for the default instance; or Crash immediately with no error messages in the logs.
This is no nearly detailed enough, I know. I'm missing error messages and more. It's snowing outside and I have to get home. I just think that the installation for this product in a clustered environment is very unstraightforward at best, and at worst is a real liability to an organization since it's practically impossible to get it clean the first time through.
According to SP1 documentation patching the Active node in a cluster will automatically apply the SP1 patch to the Passive nodes. However, I found a MS document that says if you have management tools installed on the passive node, you must patch this node separately. Is this correct?
Also, since Integration Services is not cluster-aware and therefore must be installed separately to the passive node(s), does SP1 need to be applied directly to the passive node(s) to patch Integration Services or is it automatically patched when I patch the Active node?
Our production server is currently running SQL 2005 on a stand alone machine. SQL Server is installed as a default instance.
Can we upgrade to a cluster without having to change the instance name i.e currently applications connect to this server with hostname of the server i.e SERVERA, can we install a cluster such that sql server can still be called SERVERA.
...so got the below information from the cluster log:
000009fc.00000d68::2007/02/13-12:36:53.210 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.226 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
000009fc.00000d68::2007/02/13-12:36:53.226 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] OnlineThread: QP is not online. 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 0000088c.00000af8::
Looked at the system log to see if there are any errors , but could not found any during that time....The last message in the system log was
Event Type: Warning Event Source: Print Event Category: None Event ID: 3 Date: 2/13/2007 Time: 5:03:04 PM User: NT AUTHORITYSYSTEM Computer: xxx Description: Printer ITGHP8N1 on rchprt01 (from R6911497-XP) in session 1 was deleted.
before that there were messages of creating and deleting the printer...and R6911497-XP is my laptop which was not really running during that time...
From some research came to know that this might be because of network issues, but let me know for what errors I need to look for network issues...does the above error in the system log suggests network errors...
When you try to re-apply SP2 for SQL 2005 on node added to cluster it continously fails?
Only way to apply SP2 is to shut down original node(with SP2 allready applied) and then apply SP2 and hotfixes on additional node!
I would like to see some reply from SQL support team for this 'issue'. Is this normal? This bring many issues when you have more than one sql on 2 node cluster....etc
We are trying to install SQL Server on a cluster that has 4 nodes, 3 of them running SQL2k. We're getting an error in the setup after it is done with Framework:
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache ... Source File Name: datastoremachineconfigscopeproperties.cpp Compiler Timestamp: Wed Aug 24 13:40:04 2005 Function Name: SqlInstallConfigScope.InstanceName ....- Error: Could not find an install of type 3 for instance SQL ##
We think it's due to a directory and item in the registry for a server instance we used to run on this server, but no longer due as it was uninstalled and the server moved to this cluster. The directory doesn't show in other nodes in the cluster, but does in the cluster it was moved from. We continue to find that 2nd instance refuses to failover to this server also. We have determined that it€™s only the SQL server which is having issues as we were able to move the disks over. When we start the SQL service it pops back to 2nd instances home server.
I have a two node failover cluster with SQL 2005 installed. I am running Windows Server 2003 x64 Enterprise and SQL 2005 x64 Enterprise. When I try the SP2 upgrade, I basically get an error message saying no passive nodes were succesfully patched. I have tried installing from the active node and the virtual server, same results with both. I have also tried the LMHOSTS file addition that Microsoft recommends, but that didnt solve the problem either. We do have an MSDTC Resource set up, as I have read this may cause problems, but it still doesnt work.
I dont know what to do next, any ideas?
Time: 03/11/2008 09:40:26.456 KB Number: KB921896 Machine: CAROLINA OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790) Package Language: 1033 (ENU) Package Platform: x64 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: Yes Log Location on Passive Nodes: (OAKLAND) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix (CAROLINA) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix ********************************************************************************** Prerequisites Check & Status SQLSupport: Passed ********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.2.3042 x64 Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x64 ENTERPRISE SQL Server Native Client ENU 9.00.3042.00 x64 Client Components ENU RTM 9.00.1399.06 x64 ENTERPRISE MSXML 6.0 Parser ENU 6.10.1200.0 x64 SQLXML4 ENU 9.00.1399.06 x64 Backward Compatibility ENU 8.05.2004 x64 Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x64 ********************************************************************************** Products Disqualified & Reason Product Reason ********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID ********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : Error Number : 11009 Error Description : No passive nodes were successfully patched ---------------------------------------------------------------------------------- ********************************************************************************** Summary No passive nodes were successfully patched Exit Code Returned: 11009 e : Error Description : ---------------------------------------------------------------------------------- ********************************************************************************** Summary No passive nodes were successfully patched Exit Code Returned: 11009
Have recently performed an in-place upgrade of a 2 instance sql cluster from 2000 to 2005. The upgrade process went relatively smoothly. However, I am running into problems installed sp2. The first problem that I run into is that I have resrcmon.exe locked. I can click next, which is fine, but once I get past that point I get stuck during the installation process. I am updating DatabaseServices and Integration Services. It gets stuck on 'Awaiting first complete passive cluster node SQL-Test'. Does anyone have any ideas? Thanks, Tim
I have windows server 2003 service pack 1 and sql server 2005 service pack 1 - 64 bit. Sometimes it happens in the middle of the night. Sometimes it's in the middle of the day and sometimes it's multiple times in the same day. Sometimes the server reboots, but does not failover.
We wish to upgrade our hardware of two sql boxes onto a single cluster. One of our databases will not run on sql 2005 and so I wanted to know if it is possible to run an instance of sql2000 and an instance of sql 2005 on the same cluster.
This is possible or would it cause as a lot of problems?
