Subject | Further to Performance Issue |
---|---|
Author | Todd Brasseur |
Post date | 2002-12-06T15:47:43Z |
One major change we made in our application design was to reduce the
number of tables we had for Codes and Rates. For example, in our
original (DOS) version we would have had:
Table 1 - Letters
Code
A
B
C
D
Table 2 - Numbers
Code
1
2
3
4
In the new system we created a CodeType Table
CodeType
Letters
Numbers
And a codes table that looks like
Code CodeType
A Letters
B Letters
C Letters
1 Numbers
2 Numbers
3 Numbers
This means that instead of having 30 small tables (5 to 1000 records)
we now have 4 tables (others holding rates and ratetypes). It also
means that we now are constantly selecting from the larger tables
rather than from different smaller tables.
We believe that proper indexes are in place.
Could this affect performance to a large extent?
Todd
number of tables we had for Codes and Rates. For example, in our
original (DOS) version we would have had:
Table 1 - Letters
Code
A
B
C
D
Table 2 - Numbers
Code
1
2
3
4
In the new system we created a CodeType Table
CodeType
Letters
Numbers
And a codes table that looks like
Code CodeType
A Letters
B Letters
C Letters
1 Numbers
2 Numbers
3 Numbers
This means that instead of having 30 small tables (5 to 1000 records)
we now have 4 tables (others holding rates and ratetypes). It also
means that we now are constantly selecting from the larger tables
rather than from different smaller tables.
We believe that proper indexes are in place.
Could this affect performance to a large extent?
Todd