Re: Schema Naming Standards

  • From: "Mark J. Bobak" <mark@xxxxxxxxx>
  • To: backseatdba@xxxxxxxxx, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 26 May 2015 22:30:41 +0000

Trying to start a religious war here, eh? :-)

Seriously, whatever standard you pick, stick with it.

In my opinion, having the app owner schema name end in _USER seems
counterintuitive to me, but what do I know?

In my limited experience, we had the app owner schema named after the
product, batch programs logged in as users whose names were related to the
subsystem they were associated with, and end users had logins that were
first initial and last name.

-Mark

On Tue, May 26, 2015, 5:31 PM Jeff Chirco <backseatdba@xxxxxxxxx> wrote:

I was wondering if others have a naming standard for application schemas.
Like do you had a prefix or suffix? It was started before I got to this
company that all schemas end in "_USER" and then I later added a "_APP" for
application logins to separate schemas that owned the objects and what the
application logs in as. So for example for a Payroll program the schema
would be PAYROLL_USER instead of just PAYROLL.

We are starting up a new database for a big system and the developers had
asked to drop the _USER. The _APP will not be needed since users will log
in directly to this particular database.
I am open to the idea but was wondering what is common? Part of my concern
is that one database will be different than others but really the _USER
serves no purpose.

Thanks in advanced.

Jeff

Other related posts: