This content has been marked as final. Show 3 replies
Why go to the trouble of creating a whole new database and duplicating your data? You would be better just creating a new schema for the new application and applying appropriate grants so users have the access to the data they need.1 person found this helpful
However same set of users accounts should be allowed to access both applications.Are these database users or some sort of application/business users that are stored as data in the tables etc. Too often people talk about 'users' of applications but are not really talking of actual database users, so you need to be clear of the details when explaining.
Thanks for the reply... I am referring to the oracle users... Well they are same as the application users in my case. And regarding the creating new the databases for the extension, here I will only be adding the new objects that are needed for the extension to the new database. So in this case the extension will be connected to both the original database and the new database.
Any recommendations? And any issues that I could face if I choose to create a new schema.
Napster wrote:This is a design issue, and as such a matter of personal taste.
Personally I am a great fan of schemas, and would always plump for a s separate schema for every sub-system. It is a useful way of defining application code and data, and promotes clear interfaces between sub-systems. In a large organisation, subsystems often represent different parts of the business and so have different owners; hanece the need for clarity in business rules and data access.
Any recommendations? And any issues that I could face if I choose to create a new schema.The main reason why people (i.e. developers) hate schemas is that they impose a management overhead: granting of privliges on objects and data, in both directions, and perhaps the development of additional code such as views or API packages with restricted interfaces. In my opninon these are bogus objections, born out of slackness, but it be disineguos to deny that multiple schemas do require extra typing.