Archives of the TeradataForum
Message Posted: Thu, 10 Apr 2008 @ 14:36:16 GMT
| Subj: || || Re: Controller for DBC |
| From: || || Judge, James A |
Absolutely true that you cannot create tables and macros in DBC. Best practice is to create a "superuser" under DBC (e.g. SYSDBA) and create
all customer databases and users under superuser.
The database DBC gets refreshed/updated as a matter of practice during major release level upgrades. What if your tablename, macroname was a
name that is now required by the next database release; that could cause major administrative re-work for you.
System/user resource usage and capacity tables in the DBC tend to have "custom" physical design attributes for performance per AMP (UofP). A
best practice is to create a "historical" image of "trending", "performance" tables in another administrative database where space optimization
can be applied to tables (like NO FALLBACK and multi-value compression). This allows you to save 50-80% space consumption by these history tables
and also make them more "user friendly" (as in joins to reference tables).