Re: Whatcha' wanta have?????

"Madison Pruet" <mpruet@comcast.net> wrote in message news:yCVUb.239099$xy6.1249571@attbi_s02... > As a mild diversion from the IDS-DB2 conversion thread, its time for one of > my more favorite exercises. ;-) > > We are nearing the end of the coding cycle for IDS 9.5. We've got a whole > bunch of really cool stuff in place and - well - its time to get input from > you guys as to what you want to see in the 9.6 release. > > Now, I know that everyone's favorite thing is going to be "marketing", but > I'm in development. So I need to talk features and functionality. So feel > free to send them on in. > > Just an FYI - I'll be away for a while and won't be able to get email via my > comcast email address. But, I'll be following the newsgroup rather closely. > OK... 1. Ability to be able to change the owner of anything. 2. Ability to be able to rename anything. Surely these are fairly simple? Harder ones... 1. If have have a down chunk the ability to be able to restore just that chunk and the rollforward logs on just that chunk. ala Oracle recover datafile 2. Transportable table..I mean dbspaces...ala Oracle 3. That onmode -B to flush stuff to disk (useful to reduce checkpoint times) to be documented and supported 4. Fix that bug listing in PTS where oncheck does not check everything it could i.e. a better oncheck. > Also, next week I'll be in some planning meeting. So getting responses back > fairly quickly would really help. > > Thanks > > M.Pruet > >

Also. 1. truncate table x should drop all extents. 2. create table..with no first extent size specified should not allocate an extent (why waste space if the table is not used by this particular customer e.g. SAP/Baan etc with 40,000 tables!!) 3. Ability to alter the first extent size on a table then a) a table with no extents would use this as the first extent size i.e. unused table but the customer decides they want to use a new area of the overall application suite which now needs this table to have 100,000 rows loaded. Hassle if constraints/views etc also used. b) alter fragment on table x init in .. could use the new extent size Wild stuff. 1. We have (my syntax is crap but you get the idea) create index myind on a (b) fragment with b=null in dbspace_1, remainder in dbspace_2 why need the remainder? create index myind as select a from b where a is not null. e.g. table use to sent an interface file to another system create table mytab (col1 char(20), col2 int,....,batchid integer) batchid=null until the data is write to a file to be sent to the receiving system (e.g. invoice file)... Rows gradually get put in the table, once per hour a process does a) select * from table where batchid is null b) sends this data out to the other system c) updates these rows to have a given batchid. create myind index1 as select * from mytab where batchid is null would be a much smaller index, probably with less levels!

David Williams wrote: > 2. create table..with no first extent size specified should not allocate an > extent > (why waste space if the table is not used by this particular customer > e.g. SAP/Baan > etc with 40,000 tables!!) Uhum.. yep heard about that one. -- Serge Rielau DB2 SQL Compiler Development IBM Toronto Lab