Sql performance more columns or more tables for reporting
Hi all first post for me!!
I have a sql database that was passed down to me that started of as an
access application. Since then its evolved alot. The previous developer
stored additional columns on a table instead of splitting the tables and
we are starting to report on this data ( over 1m rows) and performance is
starting to drag on some queries.
1 table is for company and contains name, reference, address details,
financial details, insurance etc.
I am thinking that we should split the table up and have tblcompany,
tbladdress, tblfinance etc. Since our reporting allows users to report on
whatever fields they want. i think it would be better to inner join
tbladdress if the user wants to report on address details, the same for
finance, insurance etc, also some companies may not have any finance
details so whats the point in having lots of null fields?
So my question is would it improve performance? I think design wise it is
the thing to do but wanted everyones tips, tricks and opinions.
Thanks in advanced
No comments:
Post a Comment