I would think that one thing you could do to simplify your life is to define
the schema name of tables according to which business area they belong. The
tablespace you put them in should be important because of how they are
accessed not necessarily who or what do they logically belong to.
This is true if you are not concerned about physically isolating tables of a
business area from others.
Tablespaces relate to physical location of data and how it is accessed and
managed.
Schemas tend to relate to how data in tables is logically related.
I know I'm over simplifying but it can be a good start for you.
HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"db2admin" <jagdip@gmail.com> a écrit dans le message de news:
1172618312.046942.4970@h3g2000cwc.googlegroups.com...
> Hello,
>
> I want to plan rearranging tables in our database according to
> business areas. say all tables in business area A will be in seperate
> tablespace or tablespaces. I am planning to monitor activity on tables
> for a month by taking snapshots on tables and then i will see if this
> rearrangement is possible.
>
> What are the factors, measures etc. i should consider for rearranging
> tables.
> anyone has done this before?
> please guide me through process and/or direct me to some online/books
> resources for the same.
>
> regards,
> jagdip
>