Re: Large table designissue
Posted by: omkar prabhu
Date: November 13, 2009 01:05PM

hey Rick,

Thanks for your suggestions. we will try this.
select distinct subpid from transactions;
is to add

we dont have index on subpid and creating index take lot of time.
We dont need BIGINT for all column we will try to remove some of them.
yes RAM is 8GB.

Regarding compound indexes, say i have 10 individual indexes on this table.what approach should we have to create compound indexes?

Today we faced an issue,where we update this table.we have replication with one master and slave. we ran a query which does mass update on this table (master instance), at same time there were select on this table slave. this cause delay in replication. Does doing multiple update (using limit) or individual update is better in this scenario as compare to mass update

Options: ReplyQuote

Written By
October 24, 2009 02:46AM
October 25, 2009 09:11AM
October 29, 2009 09:36PM
October 29, 2009 10:34PM
Re: Large table designissue
November 13, 2009 01:05PM
November 18, 2009 12:15AM
November 19, 2009 12:38PM
November 19, 2009 12:55PM
November 24, 2009 11:49PM
November 25, 2009 11:23AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.