Showing results for 
Search instead for 
Did you mean: 

MSCS installation

Former Member
0 Kudos


Im planning for new MSCS clustter installation of ECC 6.0 with SQL 2005 on windows 2003 server.

There is two nodes with one shred drive.

Assuming both nodes are MSCS clustterd and I need to start with SAP installation -

Had gone thru Inst docs too and have few pts to discuss-

Plz correct me if im wrong -

On Node 1st

- install SQL server on 1st node

- install central service instance

- install central service instance for ABAP

- clustter first node

- install central instance

On Node 2nd

- install SQL server on 1st node

- install central service instance

- install central service instance for ABAP

- clustter 2nd node

- install dialoge instance

Plz clarify these pts -

1.what is the difference between

- central instance

- central service instance

- central service instance for ABAP

2. Do we need to install Enqueue replication server on all nodes. If yes, can I find it in SQL server DVD?

3. about IPs assigment -

- do we need to have two network card on each nodes

- do wee need to have different range of IP for node to node communication and LAN access

e.g IPs Host name IPs Host name nodeA nodeB (direct commu) LANa LANb (LAN commu.)

how do we assign IPs to -

cluster grp

sap cluster grp

database cluster grp

Many Thanks


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Mani, what you are looking to do is actually.

Prep the MSCS:

1. You don't need multiple NICs. You just need to bind muliple IPs to the same NIC. You can have multiple NICS but it will be for stuff like NIC teaming (high availability setup). But it's completely optional.

2. You will need a physical IP on each of the physical nodes.

3. In addition, you will need 3 more static IPs.

- 1 static IP for the MSCS virtual name.

- 1 static IP for the SQL virtual name.

- 1 static IP for the SAP virtual name.

4. Create 2 seperate cluster groups: SQL and SAP

Install SQL:

SQL 2005 cluster install allows you to install SQL on all nodes on the MSCS all at the same time. This means, you run the install on cluster node 1 and this will install the SQL engine on the entire MSCS. No need to reinstall SQL engine again on cluster node 2.

1. Run the SQL 2005 install on cluster node 1. Choose to install both SQL engine and client components. After this step, you will have a MSCS with SQL 2005 engine running (and able to failover between different MSCS nodes), and client tools installed on cluster node 1.

2. You will however still need to install SQL 2005 client tools on cluster node 2. Just run the SQL install again, but choose only client tools.

3. Make sure MSDTC is a resource in SQL MSCS group.

Install SAP:

1. Do a cluster install. When referencing the SQL server, make sure to reference not the physical node name but use the virtual name.

2. After the cluster install, verify that SAP is not installed w/ cluster node physical name. Make sure SAP is using a virtual name too.

central instance - in classic sense, it's a instance w/ message server and a ENQ dialog process. SAP introduced a SCS (SAP Central Services) instance, which is basically the message server and ENQ as individual processes. SCS is used if you want to use replicated enqueue.

replicated enqueue server needs to run on all nodes. I am not sure which DVD you will find this, but it is definitely not on the SQL server DVD. This is a SAP technology.

Hope this helps.

Edited by: Kevin Lin on Jul 1, 2008 12:07 AM

Former Member
0 Kudos

Hi Kevin,

Firstly thanks for the responce.

Well Im planing to install SQL server just on one PC to see the options, its giving for cluster installation.

And if Im not wrong, this installation I have to start from enterpriser server directory of the SQL DVD and choose cluster installation.

Right !



Former Member
0 Kudos


After Installating SQL 2005

What can be done to verify SQL 2005 installation for SAP ??

Just to make sure tht SQL is installed properly for cluster SAP installation and we can go ahaed and start SAP installation ???



Former Member
0 Kudos

Yes, the enterprise folder is the one you want.

After installing SQL, you should:

1. Adjust memory to fixed (right click on server > properties). Set the memory to (physical - 2GB) divided by 2. The 2GB is to make sure the O/S isn't starving. Divided by 2 because in a MSCS if a physical server goes down, you can have SAP and SQL running on the same node.

2. Adjust network packet size and max degree of parallelism using sp_configure (you may have to run sp_configure "show advanced options",1). A good place to start for network packet size would be 8192, adjust as appropriately. max degree of parallelism should be 1, because you don't want to allow for a single SQL process to consume all CPUs (meaning, 1 user running a bad query can put your SAP instance to a crawl).

3. Fail the SQL instance back and forth between the MSCS nodes, to make sure it works. Connect to it via remote SQL management studio to verify.

4. Verify code page (unicode should use 850_BIN2).

You should then be ready to install SAP.

Former Member
0 Kudos

Hi Kevin,

Using sp_configure is no problem.

but adusting memory, for this I opend database right clicked on database and getting following option -

Server memory option -

Use AWE to allocate memory

Min server memory (MB)


Max server memory (MB)


other memory option

index creation memory

Min memory per query

configured value running value

Am I on right page ???

Or giv me ur email ID I will send you snap shots.



Former Member
0 Kudos

Yes, by default the min memory should be 0 with max being a very high number. Adjust this to a fixed value.

Former Member
0 Kudos

Hi Kevin,

Few question plz-

1.while installaing it givs me option to install

SQL server Database service

create sql failover cluster

Analysis service

create analysis failover cluster

Shall i go ahead with both option or just SQL server DB and failover will work ???

2.When it comes Instance name I am going with default instance.

3.after giving virtual server name, IP configuration comes in.

now here I am configuring two pvt IPs(class A and B) on

node A.

After this it ask to include other node tht is Node B

Here my question is, I am installing SQL on node A and node B is online but not logged-in.

Although Node B is included but it never giv option to configure IP for it or virtual server name for it.

So how both node will communicate or how second node will have IPs assigned ???



Former Member
0 Kudos

Here are the details which may help you.

First, some cluster items.

1. You must have a IP which is free. This needs to be able to be created in MSCS as a cluster resource and failed back and forth between nodes A and B. Just right click and select create new resource, type IP Address I believe, and enter the IP you were given and the network mask. Enable it, ping it, fail it over, ping it again. After this is successful, delete the IP from cluster (SQL install will add it back in).

2. You need to have the data drives (where you are going to store the data file for SAP - here, we use E for backup, F for tlogs, H, I, J, K ... N for data, O for log, and T for tempdb), and SQL master, msdb, tempdb, model data drive (here, we use W) in place. All of these drives needs to be MSCS resources and able to be failed back and forth between nodes A and B.

3. You should create a cluster group called "SQL Group" or something, ahead of time. Put all the shared drives in this group as resources.

First, before you start, make sure you are logged into only node A and no one is logged into node B.

Components to Install Screen:

- SQL Server Database Services + Create a SQL Server failover cluster = both checked.

- Analysis Services = Not checked.

- Create an Analysis Server failover cluster = Not checked.

- Notification Services = Not checked.

- Integration Services = Checked.

- Workstation Components = Checked (why not, might as well be able to administer the database while logged into the database).

Feature Selection Screen:

- We disable full-text search, we just don't use it.

- Select the "Database Services" primary node and enter a local drive (e.g. D:\. Don't worry about the folder, SQL will automatically create the folder stucture here. SQL won't just dump everything on root of D:\)

- Select the "Data Files" sub-node and enter the shared MSCS drive you will be using for SQL master, msdn, tempdb, and model data files. (e.g. W:\)

- Select the "Client Components" primary node, enter another local drive with folder name (e.g. D:\MSSQL_Tools. In this area, SQL does not automatically append the directory structure.)

Next Screens:

- Select default instance, it's fine.

- Enter Virtual Name.

- Enter the shared IP you tested from steps above.

- Select the cluster group for SQL you created (In this same screen, make sure you remember to select the shared drive for the SQL master, msdb, model, and tempdb - our example is W: drive).

- In the available nodes, select node B and click on Add. (Node B should not be listed as unavailable, make sure MSCS is 100% functional before starting SQL setup).

- Enter an account and password that's admin on both nodes (probably you, the sys admin).

- Enter service account SQL will run under - Should not be your account

- For the domain groups for clustered services, it's just asking for default sysadmin in the database. Just enter "Administrator" for both Server and Server Agent. If it won't accept this, try "BUILTIN\Administrators".

- Pick authentication mode, doesn't really matter here, depends on your implementation.

- Select the "Binary order for code-point comparison, for use with the 850 (Multilingual) code page" (unicode) code page.


Former Member
0 Kudos

Hi Kevin,

Many thanks for patience.

SQL is installed.

I can send my snapshots, for verification. Give me your email ID

Now Im going to install SAP too.

And after two months have to install UNIX on DB2 clustering.

Lets see how it goes. 😆



Edited by: mani sahay on Jul 16, 2008 3:00 PM

Former Member
0 Kudos

We can't post mail address here, the system won't allow you to and is against the rules. If you have any ideas on how I can verify your install, please let me know. Thanks.

Answers (0)