c# - .NET Dataset design -


i have concern designing datasets.

i told have dataset each table maintenance purpose. because frequent change in database tables expected, having 1 dataset including every tables pain make corresponding change in application.

q. approach have dataset each table ( end having 30~40 datasets each db table using stored procedure) ?

i have separate project commonly used datasets. each project include "dataset project" reference, , use including needed dataset forms, classes, etc.

q. approach makes whole system slower? if have set of datasets separate project, beneficial, since easier make change (i need make modification in 1 place)

performance wise having multiple datasets (and multiple queries) typically slower. however, on maintenance side, having single query , dataset per tables easier maintain.

it depends on how related tables are. if can use hierarchical query of related data , put in 1 dataset recommend that. if tables not related @ separating datasets , queries might best route.


Comments

Popular posts from this blog

windows - Why does Vista not allow creation of shortcuts to "Programs" on a NonAdmin account? Not supposed to install apps from NonAdmin account? -

c++ - How do I get a multi line tooltip in MFC -

unit testing - How to mock PreferenceManager in Android? -