[KULCFG-284] make it so we can use the USERS tablespace and TEMP temp tablespace for our kul*** schemas Created: 06/Feb/08 Updated: 31/Mar/10 Resolved: 31/Mar/10
|Project:||Z Archived: Foundation CM|
|Reporter:||Ailish Byrne||Assignee:||Farooq Sadiq (Inactive)|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
currently i have these comments in kuluser_maint_pk (the package we use to purge (i.e. drop/create) schemas in oracle for the daily updates, cause we're set up to use per schema tablespaces and TEMP02
– FOR NOW THIS NEEDS TO BE CHANGED TO TEMP02 FOR THE KUALI FOUNDATION DAILY UPDATE PROCESS
|Comment by Casey Boettcher (Inactive) [ 05/Mar/09 ]|
Putting aside the larger issue of the sustainability, documentation and fragility of kul-cfg-envs, I don't see why we couldn't alter the create_user function to take a tablespace name as a third parameter and default to something sane if one isn't provided.
Also, from what I've been able to glean, all of the existing RICE-related schemas use KUALI_USERS as a tablespace. What are the pros and cons of establishing a one-to-one relationship between tablespaces and schemas?
|Comment by Ailish Byrne [ 05/Mar/09 ]|
this was a decision by the cms last year. we have to use a special version of the kul maint pk function. we would like to keep our default config as simple as possible. the db import/export is not intended to be used for live production implementations where dbas might want to get fancier.
|Comment by Farooq Sadiq (Inactive) [ 29/Mar/10 ]|
For me separate tablespaces makes management easier. I am not a DBA so I have asked the UofA DBAs to see what they recommend in regards to tablespace usage.
|Comment by Farooq Sadiq (Inactive) [ 31/Mar/10 ]|
Discussed at the Kuali Technical Integration (KTI) on Mar 31, 2010. Resolved to close ticket with no change to package.
UseUserNameForTablespace CONSTANT is set to TRUE on esdbk02 package and we would like to continue to use a tablespace per SCHEMA.