c# - Architecture for reports -
we need build reports in our system. can't build them online on tables, because of 2 reasons:
- complicated logic
- we want move reports system (just publish facts them , build reports)
so, need collect facts user actions. today have job, analyze cdc changes. approach has problems:
- cdc change not fact need, must operations
- slow processing of cdc changes
but helps collect all actions (even made sql update script) , it's async (has no influence on user operation perfomance).
another way - collect facts on business logic layer, , send them system or save table. it's synchronously operation, , difficult collect facts made sql scripts.
so, optimal way it? requirements:
- collect changes/facts (even made sql scripts)
- has little influence on user operations perfomance
i assume don't want report transaction server. may need setup reporting server via replication ( merge or transaction replication).
Comments
Post a Comment