November 25, 2008 at 5:24 pm
I'm curious to know how everyone else handles code behind SRS. Is it better to create stored procedures and views or simply put the code into the SRS report? I believe we should be putting the code into sprocs and views, but my programmer disagrees. Any suggestions or arguments to back up one way versus another?
Thanks!
Thanks!
November 26, 2008 at 9:45 am
IMO - Stored procedures are the best.
I keep finding limitations in data manipulation (sums, totals, distinct counts) on the RDL design, so the use of a stored procedure gives me the flexibility to do calculations on the SQL side where you can manipulate data endlessly.
In turn, my procedures gather data from views so you don't have to write 20 joins in each procedure.
Another added bonus is the ability to gather performance metrics automatically in a SQL2005 environment with the built in performance based reports.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply