Guidelines for need to consider for SSRS report development.

Question

Guidelines for need to consider for SSRS report development.

Saintmount.Sql

Ten Centuries

Points: 1023
More actions
February 27, 2012 at 8:02 pm

#391667

HI,
Could you please let me know what are factors need to consider for estimating the SQL Server reporting development in order plan the report as simple, medium, Complex.
Can anyone tell me what are the factor need to consider, whether report is simple, medium, Complex?
Thanks,
VJ

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Sean Lange SSC Guru Points: 286590 More actions · Answer 1

Saintmount.Sql (2/27/2012)
HI,
Could you please let me know what are factors need to consider for estimating the SQL Server reporting development in order plan the report as simple, medium, Complex.
Can anyone tell me what are the factor need to consider, whether report is simple, medium, Complex?
Thanks,
VJ

I am not sure what you are asking here. Keep in mind that what one person considers simple another person may consider complex. The same would true of development effort/duration. There is no formula that can identify the complexity of a report.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

Daniel Hallam Mr or Mrs. 500 Points: 586 More actions · Answer 2

There is nothing clear cut, as its all dependent on the developer.

Break it into time estimates to get the data and writing the report layer.

For data I'd consider factors like:

- Complexity of query

- Does the Source Data already exist or is it for a System being built

- Familiarity with Source Data

- Level of Data Integrity in Source Data

- If you have to make changes to Source Data (i.e. add columns\tables to a Data Warehouse)

- Desired performance in returning the data

For report layout I'd consider:

- Level of detail in design requirements (i.e. are their exact layout, fonts, margin, etc requirements)

- Audience (i.e. a report for an external customer may imply more time spent on the layout then a data dump for an internal auditor)

- Number of Design Elements (single table vs 4 tables and 6 graphs)

- Design Elements that you consider time consuming (e.g. writing a lot of expressions to control dynamic elements)

- Design Elements you are unfamiliar with

Saintmount.Sql Ten Centuries Points: 1023 More actions · Answer 3

Thank you so much. We are trying analysis & priorities the report complexity based on the certain constrain (Generalized manner-it’s not based on requirement).

I got input from your points. Thanks.