Does no. of tables affect database speed?

[Raymond]

Hi, I am working on a database which has various no. of small tables. I want
to combine all these tables into 1 table so that the no. of tables in the
databse are reduced. My question is will this procedure increase the
efficiency of the db as a whole( because previously the tables were of small
size and large in no. ; now they are lesser in no. but have large size...) ??

 

[pietlinden]

Hi, I am working on a database which has various no. of small tables. I want
to combine all these tables into 1 table so that the no. of tables in the
databse are reduced. My question is will this procedure increase the
efficiency of the db as a whole(  because previously the tables were of small
size and large in no. ; now they are lesser in no. but have large size...)??

why do you have separate tables for the same data? If your indexing
is good, your response time should be fine.

 

[Raymond]

I do not have same data...Actually I am being provided with a pre-defined
database which I have to improve upon..So I am trying to find some of the
common links(entities) that can connect some small tables...So that's what i
want to know that is this process useful?

 

[pietlinden]

I do not have same data...Actually I am being provided with a pre-defined
database which I have to improve upon..So I am trying to find some of the
common links(entities) that can connect some small tables...So that's what i
want to know that is this process useful?

Normally, individual tables describe different "entities" or real
world things, and these entities are related (hence the ability to
create relationships between them). If these entities have exactly
the same relationship to some set of other entities (tables), then you
can. Not always a good idea, though. Having some extra tables is not
a big deal. I find I have problems when database tables do not
describe ONE (and ONLY ONE) thing. Having multiple tables doing that
means writing union queries, which are a PITA.

 

[John W. Vinson]

Hi, I am working on a database which has various no. of small tables. I want
to combine all these tables into 1 table so that the no. of tables in the
databse are reduced. My question is will this procedure increase the
efficiency of the db as a whole( because previously the tables were of small
size and large in no. ; now they are lesser in no. but have large size...) ??

How are these tables related - both in terms of database relationships, and
(for this question more importantly) in terms of logical relationships? Do a
lot of these tables have the same "shape" - similar or identical field
datatypes, sizes, and significance? Do they logically refer to specific
subsets of a larger set of records? Or are they differently shaped tables
containing data about different *kinds* of entities?

More info please!

 

[Raymond]

I'll list some of the tables which am planning to remove from the db
itself... These are:-

1. Customer Group

This contains 2 fields, namely ID and Description (i.e. to which industry
the customer belongs..bla bla...)

2. Delievery Method

2 fields again, Method_ID and Description..

3. Delievery Time

Similar to above, description(like 2 weeks in advance.....) but this 1 does
not have any other field.


These are few of the tables( few more in the pipeline) which am thinking of
combining into 1 since they are being used in various forms.. THE PITA is
that these tables actually don't have too much of data in them, but still are
vital to the db.

I think this much detail wud b enough, if you need any more, please feel
free to tell me...