cancel
Showing results for 
Search instead for 
Did you mean: 

DB Installation for a separate instance

Former Member
0 Kudos

I wanna keep my both DEV and QTY systems on a same machine and need to keep the DB instance (QTY)different as one should not depend on another instance.Installed the DEV server and now about start Installtion of QTY system.

Should I do the MSSQL DB installation again with a different instance name then sapinst.exe ( if yes, steps please)

If I start sapinst straight away and assigning the new DB installation during custom installation..would it start a separate instance which is independent of existing DEV system..

Please clarify as I need to start my QTY system Installation.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi dude!

I fully agree with Joey; I just provide more information so that you learn more on this topic.

According to [note 171929|https://service.sap.com/sap/support/notes/171929] ( Several R/3 Systems on one SQL Server 7.0 ), there are three options to share a database server among several SAP systems, namely:

1. Multiple databases

With this procedure, a separate <SID> database is created on the same SQL Server instance for each SAP system.

2. Multiple instances

With this procedure, a separate instance of SQL Server 2000 is created on the same server for each SAP system.

3. Multiple schema (MCOD)

With this procedure, several SAP instances share both the SQL Server 2000 instance and the <SID> database.

This note, however, concentrates on the "Multiple databases" variant, as it was the only available method in SQL Server 7.0.

[Note 209596|https://service.sap.com/sap/support/notes/209596] ( Setting up Microsoft SQL Server 2000 ) recommends to read the paper 'Installation of MS SQL 2000 in an SAP Environment' available on the MS SQL Tools CD in the file readme.pdf (see section IV of the note: "MULTIPLE INSTANCES ON MS SQL SERVER 2000"); find it at:

[http://service.sap.com/msplatforms|http://service.sap.com/msplatforms]

(left pane)

-> Platform-Specific Information

-> Microsoft

-> SQL Server

All the new installations are MCOD, so you can install a large number of SAP systems in one single database instance; take only into account that these systems will be at the same database patch level. If you need to apply a DB patch you will need to schedule a maintenance window for all of them, but you will also save a lot of time installing patches.

For more information, check notes:

[388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]

[75354 - Multiple SAP Instances on NT|https://service.sap.com/sap/support/notes/75354]

[28505 - NT: Several R/3 systems on one host|https://service.sap.com/sap/support/notes/28505]

[21960 - Several instances/systems on one UNIX computer|https://service.sap.com/sap/support/notes/21960]

Do not dismiss to visit the [SAP on Microsoft SQL Server SDN page|http://www.sdn.sap.com/irj/sdn/mss] to learn more on SAP systems and SQL Server.

Cheers!

Answers (1)

Answers (1)

Former Member
0 Kudos

You can install a named SQL Server instance, and then point to that instance in the new SAP system install, but it is unnecessary.

I have installed many systems for clients who want multiple SAP systems on a single machine (for economical reasons). You can have DEV and QAS databases in the same SQL Server instance and they will not be in any way dependent on each other. In fact, running it this way will be more efficient than separate SQL instances because you will not be doubling the SQL Server overhead.

A few things to keep in mind:

- you do not want a development or quality system sharing resources with a production system.

- each SAP system by default will try to use up all system resources, so make sure to limit that by using the PHYS_MEMSIZE parameter in each system's instance profile