Best Practice - Views for SSRS

Question

2.50/5 (2 votes)

See more:

SQL-Server-2008

, +

I'm new to SSRS and wanted to get an idea of Best Practices regarding Views. Our users want to report against many tables and to make things easier I have created views with multiple tables with the necessary Joins, etc. That all works fine.

My concern is how to manage all of these views. Our finance dept wants some columns visible and others not. So does Claims, etc, etc. Even within one dept they want restrictions based on a class of users.

I know I can make custom Views but that seems to be a maintenance problem down the road.

I was thinking of creating a store procedure that could determine who the user is, what dept they belong, etc and create a return TableSet. This way I have only one place to make changes.

Any ideas?

Posted 25-Oct-12 9:34am

PaulSkopje

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-10-25T18:28:00

First, if you have finance and claims departments demanding something directly related to the database schema, including visibility of columns, it means that you are working in the organization totally corrupted by a number of organizational anti-patterns:
http://en.wikipedia.org/wiki/Anti-pattern#Organizational[^].

It also indicates that the company simply does not have appropriate software for internal business users.

Don't ask me how to survive in such situation — I have no idea and not sure if it is possible. :-)

As SSRS is nothing but a reporting tool, it should be totally agnostic to views. This is the whole idea of views — to have client software agnostic to them. The managing views it simply unrelated to reporting.

—SA