By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,851 Members | 1,752 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,851 IT Pros & Developers. It's quick & easy.

one performance question...

P: n/a
HI,

I have an performance questions...
is # of tables in one tablespaces matter for performance point of view?

why?
if yes, how many tables in one tablespace is good ?

Thanks for any suggestions?

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
"jane" <es**********@yahoo.com> wrote in message
news:11*********************@g49g2000cwa.googlegro ups.com...
HI,

I have an performance questions...
is # of tables in one tablespaces matter for performance point of view?

why?
if yes, how many tables in one tablespace is good ?

Thanks for any suggestions?

There is a big difference on this subject when comparing DB2 for z/OS and
DB2 for Linux, UNIX, and Windows. On the later, it does not matter and is
basically a matter of administrative ease.
Nov 12 '05 #2

P: n/a
Mark A wrote:
"jane" <es**********@yahoo.com> wrote in message
news:11*********************@g49g2000cwa.googlegro ups.com...
HI,

I have an performance questions...
is # of tables in one tablespaces matter for performance point of view?

why?
if yes, how many tables in one tablespace is good ?

Thanks for any suggestions?


There is a big difference on this subject when comparing DB2 for z/OS and
DB2 for Linux, UNIX, and Windows. On the later, it does not matter and is
basically a matter of administrative ease.

I usually put small tables together in SMS tablespaces.
Large and heavily used tables I put in separate tablespaces.
One disadvantage of having multiple tables in a tablespace is that if
for some reason the tablespace goes offline, during LOAD for instance,
tables in that tablespace are not available.

--
Anton Versteeg
IBM Netherlands
Nov 12 '05 #3

P: n/a
Thanks all for the info.

My case is I already have 200 tables in one tablespace, I need to
create another 70 tables, they are fact tables.. So I'm considering if
I need to create a separate tablespace or put in the exiting one...

My environment is UDB on AIX.

I'm more concern about read/write performance impact?

Is there any I/O impact about this?

( from OS point of view)?

any suggestion is appreciated.

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.