This should not be a problem. Remedy simply alters the ddl for the create table statements when that parameter is changed. The effects on the dml (select, insert, update) should not be impacted by alterations made by your dba. Just make sure Remedy is down when your dba's are making the changes.
Axton Grams On Oct 30, 2007 6:50 AM, Konstantin Pavlov <[EMAIL PROTECTED]> wrote: > ** > > > > Hello all, > > > > Remedy 7.0.01 patch 004 > > Server Group > > > > DB:10.2.0.2.0 64bit > > > > > > We have this issue: > > > > We need to change our default value of DB parameter "create storage in row", > because our db is 64GB > > and we want to reduce size of it. > > > > "storage in row" clause is described in > http://download.oracle.com/docs/cd/B14117_01/appdev.101/b10840/mm_dba.htm > > > > > > Before some months we change it from remedy admin tool -> Server Information > -> Database -> Store Clob in Row, > > but this is available only for new created forms and with clob for storing > of data – like HPD HelpDerk. > > > > > > My question is: > > > > If we change this parameter to True for existing tables (directly in db) > and our db admins recreate tables > > (export and import data) should this cause future problems for our prod > Remedy data and/or db? > > > > > > Best Regards > > > > Konstantin Pavlov > > __20060125_______________________This posting was submitted with HTML in > it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
