(Cluster) Memory settings

Hello, I am purchasing a HP DL-380 (Cluster)
I am planing to install Windows 2003 and SQL 2000
Both machines has two processors and 4 GB o Physical Memory (RAM), but I
want to put 6 GB in the
Active Machine and 2 GB in the Passive Machine.
So, That is possible?
1) Is possible to have differentes memory configuration in a cluster?
2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
Thanks a lot!!
AA
I forgot to mention that both machine are with 32 bits processors
Thanks again
AA
"AA" <aa@.personal.net.py> wrote in message
news:%23K0V94MIEHA.2376@.TK2MSFTNGP12.phx.gbl...
> Hello, I am purchasing a HP DL-380 (Cluster)
> I am planing to install Windows 2003 and SQL 2000
> Both machines has two processors and 4 GB o Physical Memory (RAM), but I
> want to put 6 GB in the
> Active Machine and 2 GB in the Passive Machine.
> So, That is possible?
> 1) Is possible to have differentes memory configuration in a cluster?
> 2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
>
> Thanks a lot!!
>
> AA
>

(Cluster) Memory settings

Hello, I am purchasing a HP DL-380 (Cluster)
I am planing to install Windows 2003 and SQL 2000
Both machines has two processors and 4 GB o Physical Memory (RAM), but I
want to put 6 GB in the
Active Machine and 2 GB in the Passive Machine.
So, That is possible?
1) Is possible to have differentes memory configuration in a cluster?
2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
Thanks a lot!!
AA
Do not do this. Just remember that some day resources from node one with 6GB of memory failover to node 2 with 2GB of memory. What will you do then
rgds
Sinisa Perovic
|||What you will do then is exactly what everyone has to do who is running a
configuration with dissimilar processing capacity. You plan for the case
where both are running on the node with the least power. You estimate the
degradation in performance for the applications based on various load and
time scenarios. You then make a business decision as to whether that
degradation in performance during that specific downtime scenario is
acceptable or not. If it is acceptable, you configure it and off you go.
If it isn't acceptable, you come up with alternatives. Saying to not ever
do this is a very simplistic answer that simply is not correct.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

"None of the selected features can be installed" error on SQL 2005 Cluster

Hey All,

I installed SQL 2005 on a cluster. Everything on the primary node works fine. However, as the documentation suggests, the SQL Management Studio (and other tools) are not installed on the standby node by default. However, when I go to try and install on the 2nd node I get the following error:

TITLE: Microsoft SQL Server Setup

None of the selected features can be installed or upgraded. Setup cannot proceed since no effective change is being made to the machine. To continue, click Back and then select features to install. To exit SQL Server Setup, click Cancel.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=SQLSetup90&EvtType=28108

The link is referencing something about requiring a complex SA password. I can verify that the directory structure on node 1 where the management studio and client tools exist does not exist on node 2. I'm at wits end here, I've tried uninstalling/reinstalling/everything.

Anyone have any ideas?

thanks!

I finally figured it out... Although the original install didn't actually install any of the tools on the 2nd node, it did create a "tools" directory on the 2nd node. I renamed this directory and then went to try and install the tools and it worked. Evidently the SQL setup was just looking to see if this directory existed.

$#@$#%! SQL 2005 Cluster Install!

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.

For a premier product, this installation SUCKS.

Whooo. Okay. I feel better.

Here's my situation:
4-node Cluster (Windows 2003 Enterprise Edition), SP1
SQL 2005 Enterprise Edition

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.

Regards,

hmscottI had a very similar problem recently involving a Windows 2003 cluster and an active / active install. I had to give the userid I was using explicit full permissions on the WINDOWS/temp folder on the secondary machine before the install would complete successfully, even though the account I was using was a domain admin.

It's certainly a stab in the dark, but may be worth a try|||I was able to complete the 2153 patch process by deselecting one of the nodes (ie, but only choosing to do one node at a time.

The other #$!#@.! I hate about using the 2153 patch is that it must be run on all the nodes for the non-clustered services (notification services, SQL Tools, integration services).

I love SQL 2005. I expect to earn a substantial part of my income for the next 5 years from SQL 2005. But I sure do not like the installation of SQL 2005. I hope that they get these issues resolved by SQL 2008.

Regards,

hmscott