Install MSDE on W2003 cluster
-
How can i install the SQL MSDE (sp3a) with a instance name on a windows 2003 cluster server.
A custumer has a windows 2003 cluster server. When i run our setup, MSDE SP3a included, with parameters like intsance=myprogram, the software installs normaly on the server. The software installs correctly.
Our client software louks for %Server%\%InstanceName% across the network.
I used the svrnetcn.exe to configure the tcp/ip protocol, and set the port to 1433. I test with the sql enterprice manager, to connect the msde on the 2003 server. This don't work.
The software don't see the instance name.
When i install the same msde software on a nomal Windows 2003 server everything works fine.
What else can i do? What can there be wrong?
Thanks for your reply.
-
I don't believe that MSDE is cluster aware. You should see it on the node that you installed it on, but not on the clustered node.
-
Sorry Steve,
i believe it can work on a cluster.
Do you have a url or docs about this, then i wil believe your message.
-
Maybe I'm wrong, but the MSDE version is based in the Standard version of SQL Server, witch is not cluster aware.
But not everything is lost! If I were you I would try these two alternatives:
1) MSDE creates a service inside each machine. Put the database (MDFs and LDFs) inside the shared storage resource and the service name as a common resource inside the MSCS (with IP, hostname, etc). After this, add the virtual server name inside each SQL server installation and change a parameter - witch I don't remember now - to the new IP address.
2) The prompt command CLUSTER can have an answer to your problem. Try this inside a cluster machine with the MSCS service.
Good luck! Don't forget to send us news about the resolution of your problems.
-
Only Enterprise Edition is Cluster-aware. Check Microsoft's SQL Server website, for the description of the versions. Only Enterprise Edition says that it can be clustered.
-SQLBill
-
Hi SQLBill,
i like to install the MSDE on a cluster, but it haven't to be cluster aware.
In this case it isn't a problem when the MSDE is always in the air.
On 1 of the cluster server is already a MSDE installed with a default setup, (no instance name). We will install our MSDE with instance on the outher server.
By the way, our client software sees the default msde install the one whitout the instance name. Our client software don't see our instance name.
Thats the problem.
-
What kind of cluster do you have? Active/Passive or Active/Active?
On the issue of installing MSDE on a cluster, I know I was thinking that you wanted MSDE clustered so it could 'fail-over' and I think that's what everyone else thought you were trying to do - not install two separate instances of MSDE. You can install separate instances as you found out. You just can't 'cluster' them so they will fail over.
Since MSDE isn't clustered, if you only have Active/Passive cluster you will only be able to see the MSDE that is on the node (server) that is currently ACTIVE.
-SQLBill
-
Hi,
our client has a Active/Active 2003 cluster.
Something else,
On the server A we installed our MSDE\Instance.
On server B is a standard MSDE installed. On this server we run (msde) Sql Server Service Manager.
Whit this tool we can see our server A\Instance running.
(But the clients don't )
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply