I have a database with a lot of data and everything is neat, normalized (within reason - using EAV), and I have stored procedures for accessing and modifying data.
I also have a WinForms application that users download to search and view this data (without inserts). To make things easy to use and update, I used SQLite to store this data, and it works very well.
I am working on updating the whole process, and I was wondering if I should use the denormalized representation of the data to send to users, ala 1 table with all the properties in the form of columns, or continue to use the same schema as the main database?
My initial thoughts are as follows:
Denormalized view:
Benefits ... Provides a simple method for querying data (since I don't do many joins, just a bunch of column searches.
Cons ... I would have to manage a second level of data access. Of course, I do not think it will be difficult, but it is still a little more.
If a new property is added, I will have to change the schema again and make changes for the changes. If I can just request a property package and a working form there.
:
...
, , , , SQLite .
...
.., DAL.
?