Cluster nodes

Hi All,

I've heard in a presentation that the number of supported nodes in a cluster on 64bit system is going to be limited to 4. Can you confirm that?
What about the number of instances? These are the informations that I have:
25 in a cluster (a drive letter is required per cluster group)
50 in a standalone server with Enterprise Edition
16 on the other Edition
Can you confirm as well?

Thanks for your response.
JeromeSQL Server 2005 Enterprise Edition will support as many nodes as the underlying operating system supports .. which is 8 nodes in current versions of Windows (in the editions that support Server Clustering). So the maximum number of nodes is 8, and that's true for both 32-bit and 64-bit.

In SQL Server 2000 32-bit edition the limit is 4 nodes, but the 64-bit edition supports 8 nodes.

Your instance numbers are correct though your number of 25 on a cluster is likely too high: typically you have the drive letters A:, B:, C: already assigned to local drives, so that leaves 23 letters for the cluster groups, and for a shared quorum cluster one more drive letter (Q:?) will be needed for the quorum drive, so that leaves 22. So 22 clustered instances is a more realistic limit, though with an MNS (Majority Node Set) cluster where the quorum info is kept on the local drive of each node you could get 23 clustered instances.

Thanks,

Don|||The maximum instances I have seen on MS SQL 2005 is 16 instances on 4 nodes.

Cluster nodes

Hi All,

I've heard in a presentation that the number of supported nodes in a cluster on 64bit system is going to be limited to 4. Can you confirm that?
What about the number of instances? These are the informations that I have:
25 in a cluster (a drive letter is required per cluster group)
50 in a standalone server with Enterprise Edition
16 on the other Edition
Can you confirm as well?

Thanks for your response.
JeromeSQL Server 2005 Enterprise Edition will support as many nodes as the underlying operating system supports .. which is 8 nodes in current versions of Windows (in the editions that support Server Clustering). So the maximum number of nodes is 8, and that's true for both 32-bit and 64-bit.

In SQL Server 2000 32-bit edition the limit is 4 nodes, but the 64-bit edition supports 8 nodes.

Your instance numbers are correct though your number of 25 on a cluster is likely too high: typically you have the drive letters A:, B:, C: already assigned to local drives, so that leaves 23 letters for the cluster groups, and for a shared quorum cluster one more drive letter (Q:?) will be needed for the quorum drive, so that leaves 22. So 22 clustered instances is a more realistic limit, though with an MNS (Majority Node Set) cluster where the quorum info is kept on the local drive of each node you could get 23 clustered instances.

Thanks,

Don|||The maximum instances I have seen on MS SQL 2005 is 16 instances on 4 nodes.sqlsql

Client alias on 64bit server

We have just upgraded a 32bit server to 64bit Windows 2003, we had client
alias working correctly before when os was 32bit but now we have gone to
64bit i can't get any aliases to work.
I've tried configuring exactly the same alias on a 32bit machine and that
works but if the server is 64bit then no joy, even if try to create an alias
to the local 64but machine.
Any help would be gratefully appreciated.
Same problem here with XP 64. I've tried both 2000 and 2005 with the same
problem. It simply ignores the port and goes for 1433. Oddly enough, ODBC
worked (setting the port on the second screen).
"Adam Shepherd" <Adam Shepherd@.discussions.microsoft.com> wrote in message
news:95F13D92-FBC9-4FD9-8C0B-AB4D3EF8370F@.microsoft.com...
> We have just upgraded a 32bit server to 64bit Windows 2003, we had client
> alias working correctly before when os was 32bit but now we have gone to
> 64bit i can't get any aliases to work.
> I've tried configuring exactly the same alias on a 32bit machine and that
> works but if the server is 64bit then no joy, even if try to create an
> alias
> to the local 64but machine.
> Any help would be gratefully appreciated.
|||I've done a bit of playing around and i think what's happening is that the
alias is being written to the 32bit registry but sql server is trying to read
from the 64bit registry. If i create an entry in the 64bit registry then
alias works ok. The registry keys are:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ MSSQLServer\Client\ConnectTo
and:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\ConnectTo
Looks like an issue with SQL Server, but if the key is in boht locations
then aliases work.
hope that helps,
Adam
"Scott Wallace" wrote:

> Same problem here with XP 64. I've tried both 2000 and 2005 with the same
> problem. It simply ignores the port and goes for 1433. Oddly enough, ODBC
> worked (setting the port on the second screen).
>
> "Adam Shepherd" <Adam Shepherd@.discussions.microsoft.com> wrote in message
> news:95F13D92-FBC9-4FD9-8C0B-AB4D3EF8370F@.microsoft.com...
>
>