Archives of the TeradataForum

Message Posted: Thu, 07 Apr 2011 @ 14:23:53 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Thanks Geoff and that will be true if anyone uses 'individual ID's' to create objects.

THAT, depends on one's 'standards' and 'internal architectural' constructs. It would behoove James and 'his team' to reconsider this practice. I have always recommended that the DBA set up 'specific' User accounts (I'll all them ADBA ccounts - Application DBA) that are used by development team leads, etc. that are 'authorized' to create table/view/macro/etc. objects within DB/User 'containers'. Developers should only be able to create 'objects' in one's sandbox (or what ever that is in one's environments) and when they are ready to move code, etc. into 'systems test', there is a process that allows the 'team lead ADBA' to then create the objects in the 'real' DB going forward. So, the 'owner' of the object is not a person, but a 'position' that has responsibility and if one disappears, it is not an issue.

Also, one might want to consider what 'function' creates what - for example, the head DBA uses a specific ID (e.g. SYSDBA?) to create all DB and User containers and all other 'objects' are created by either the DBA or the ABDA accounts.

Again, this is just one suggestion/method. I guess the key is, no matter what one ends up with, make sure it has been established through good 'engineering' principles, methods and procedures and not just a 'ad hoc' approach.

As always, just my thoughts for what they are worth on today's market;-)

JK

	<Prev	Next>		<<First	<Prev	Next>	Last>>