c# - RDLC parameters filter after records pulled -
i'm trying determine best practices client-side reporting using reportviewer displaying rdlc. when designing report, can specify parameters pass report can used filter records. using sql profiler, however, when running report appears filter applied after records pulled down report. seeing correctly?
if so, why isn't kind of thing discouraged? shouldn't records filtered perhaps @ dataset level or @ point such records filtered prior being sent client (for performance reasons, of course)? have looked , looked discussion of these kinds of issues on internet , see multitude of ways implement parameters (ie, how to) no discussion of when 1 way better , why. isn't new, expect there more out there. can point me discusses if have missed something?
i experimented client side rdlc , came conclusion data handling inefficient. point out, encountered issues parameters not filtering you'd expect. used crystal reports (on think based) 10 years ago , i'm sure there wasn't issues this.
the best method used pre-prepare dataset before generating report. found passing data @ runtime, not defining data access in report definition ensures ever use data provide.
you right, there's little documentation/discussion on using this, ended removing project , using other methods render charts/tables etc.
Comments
Post a Comment