| Naming convention - schema names [message #632715] |
Wed, 04 February 2015 21:23  |
 |
aimyee
Messages: 5
Registered: February 2015
|
Junior Member |
|
|
Any recommendations on naming conventions for schemas in an oracle database.
Is it a best practice to
1. Use the same schema name across environments
Example in a development environment create a schema call MPGroup
And in test create the same schema called MPGroup or
2. Differentiate the environment in the schema name.example in the development instance call the schema devMPGroup and in production call the schema prdMPGroup
If you have any documentation to support your opinion I would be grateful.
Thanks!
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Naming convention - schema names [message #632747 is a reply to message #632726] |
Thu, 05 February 2015 03:37  |
cookiemonster
Messages: 13961
Registered: September 2008
Location: Rainy Manchester
|
Senior Member |
|
|
Depends - are these schemas that contain objects?
If so, same name, always. I can't think of a single benefit to using different names - To be absolutely clear, the ability to stick dev and test in the same DB is not a benefit and will just cause trauma if tried.
Why does business think it's a good idea?
|
|
|
|
|
|
| Re: Naming convention - schema names [message #632754 is a reply to message #632753] |
Thu, 05 February 2015 07:01 |
Lalit Kumar B
Messages: 3174
Registered: May 2013
Location: World Wide on the Web
|
Senior Member |
|
|
If they are different databases, then by having different schema names in respective DBs will only create confusion. A small example, if a synonym is to be created, you need to change it everytime it moves into a different environment. How would developers check in their code? How would version control tool be used for the source code?
Perhaps, you could first ask the business guys why they think otherwise. Let us know their response.
[Updated on: Thu, 05 February 2015 07:03] Report message to a moderator |
|
|
|
| Re: Naming convention - schema names [message #632756 is a reply to message #632754] |
Thu, 05 February 2015 07:33 |
cookiemonster
Messages: 13961
Registered: September 2008
Location: Rainy Manchester
|
Senior Member |
|
|
At some point in various processes you're going to have to tell things where all the tables are.
This may be through synonyms, login details for external clients, changing the default schema on login.
If you have the same schema name in all cases all the above is static and doesn't need to be reconfigured correctly on each DB and retested every time you change anything.
Exact problems depend on external clients and how they connect.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
