| Data Architecture (DA) / Database Admin (DBA) [message #153873] |
Wed, 04 January 2006 10:04 |
donlcs
Messages: 62
Registered: October 2005
Location: VA, USA
|
Member |
|
|
I guess each has a bit different role but share certain trait.
Now, some specifics.
Assumptions:
a fairly large database (be it Oracle, SQL Server or DB2), over 100 user tables, 800 MB + data, supporting 3 ~ 5 applications.
Here are some KISS-based preliminary thoughts on the core of DA pertaining to this existing database, let me know what you think.
1) Data Class
Knowledge of all these user tables and interrelationships on data end (logical model kicks in here). I call this class the base.
2) Fair understanding/knowledge of which tables are for which system/applications (imply understanding of related applications and systems as well) and which ones are common/shared/global
Some intelligent table naming convention may help here for everyone.
3) Service Class
All udfs, procedures and packages belong here. Now,
*) Intelligent naming convention would be one way for better support and maintenance.
*) Having a current document capturing all the metadata for these objects would be good as well.
4) Security Class
I'm weak on that so I'll skip it here.
5) Enterprise (Architecture) Alignment Class?
How well does this database fit into the overall schema of "things" - the big picture of the enterprise or how important or not important it is? Hence, sort of rate it/give it a weight if/when one is responsible for several huge databases.
I'm just thinking loud here...
Thanks.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
