Re: Using one development instance for multiple applications

Marc,

What a mine field you could create doing something like this. It all depends on what each development area is used for and if any of them use external applications. The obvious issues might include group 1 wanting the database upgraded to version b (for an application upgrade) while group 4 needs the database left at the current version. Consider group 8 who needs the database rebooted to effect a parameter change - but groups 1-7 refuse to have their work interrupted during business hours.

I have had experiences with different SAP development groups on the same machine - (not even the same instance) - and often came across issues of needing to reboot the machine for one group while the other refused to be inconvenienced by it (adding disk etc). I've also had a couple of PeopleSoft databases on the one machine sharing Oracle Software - and had issues with one needing to upgrade the operating system and oracle version to effect an upgrade (financial) while the another group (HR) said they did not want it. Even worse - one group regular ran large reports that slowed the other group down dramatically.

Simply put, this decision should never be made based on the bottom line alone. The partitioning of systems should be based on use and autonomy requirements.

Regards

Doug Carter
Database Administrator
TUI Consulting

Marc van Maanen wrote in message <354E32F3.13E5_at_xs4all.nl>...
>Hi,
>
>we are planning to buy and install a new server for development/test
>purposes (RS/6000 F50 AIX ). The intention is to replace 4 old
>uni-processor systems with all their instances (about 20) and create
>just one instance on the new server
>
>I have the following questions:
>- Is this advisable (and if not: howcome ?)
>- Does anybody has experience with this
>- What are pitfalls and/or prerequisites to keep in mind
Received on Tue May 05 1998 - 00:40:57 CDT