Re: Using Service Names for database

From: Steve Harville <>
Date: Thu, 19 Feb 2015 20:28:45 +0000
Message-ID: <>

Hi Jeff,
It is a good practice, especially on RAC. We create services for each distinct workload. For instance the Warehouse Operations group use a service that is different from the Order Management group. This way we can "pin" one type of workload to it's own node and another type of workload to a different node. This reduces the interconnect traffic between nodes since the different services are not updating the same data blocks. Steve

On Thu Feb 19 2015 at 2:44:29 PM Jeff C <> wrote:

> Does anybody use or have experience with using multiple Service Names for
> your database? Is this a normal thing people do? I have a database that is
> a mix of a bunch of different applications and I would like to better
> identify them from database connection and so giving them their own service
> name to connect to seems like the perfect fit. One thing I did noticed
> that we will have to be careful about is if you restore that database to
> the same server with a different name and you don't change the service name
> parameter then the listener will pick up that service name and your users
> may be going to the restored database and not production.
> Any other things to think about and/or is this a bad practice?
> Thanks,
> Jeff

Received on Thu Feb 19 2015 - 21:28:45 CET

Original text of this message