SSRS Best Practice documentation

Posted on 2010-11-17
Medium Priority
Last Modified: 2012-05-10
We have recently split out some of the people in our reporting department and have to do some documentaion. In our DW group, amonng other things, we control the reporting servers and all encompassing administration. In several of departments (ie. Finance, HR, etc.) they each are now assigned a report developer that will be considered the subject matter expert in that area. These individuals jobs are to work within their respective departments and either create a report, or have the DW group create it if it's a bit more complex. The developers have limited permissions and will no longer be able to create objects on the servers.

Now to the question ... One of the first items on the adjenda is to create a Best Practice doc on the seperation of responsibility between the DW team and the developers (ie. Admins create objects, developer use embedded SQL, etc.).  In your travels over the internet, have you seen any documentation that others have created that would relate to this.

I hate having to create it from scratch and have started that way, but as always, there will always be things left out that hopefully someone else has thought of and posted.
Question by:aelliso3
  • 3
  • 2
LVL 10

Accepted Solution

itcouple earned 2000 total points
ID: 34158488

I would start with this (it is more high level but before diving into details I would first read that) http://www.joelonsoftware.com/articles/fog0000000043.html

Our new team started with 2/12 after 4 months time we score 11/12 :) Development it is so much easier !!! Simple but effective!!

p.s. I have seen detailed ones yet.

LVL 10

Expert Comment

ID: 34158501
I have = I haven't
LVL 11

Author Comment

ID: 34158730

That's a good start ... I see one miss in my doc already

I soooo hate doing these, but someone has too ... :-}
LVL 10

Expert Comment

ID: 34159859
Unfortunatelly someone has to do it and if someone has to do it then +1 point :)

Here are some links but they don't go into the lowest level of details (responsibilities) which I presume is usually company specific

BI Developers (in some places) have full access to development box which is under source control (Database project! + BIDS projects) Dev QA for developers use, QA Env to Test deployment + tests. No Access to production/QA for developers. Deployment should be done by DBAs on Prod+QA.

Also Change Control systems should be in place for Production (and sometimes QA).

Using Iterations is usually very helpful for managing smaller portions of projects instead of one big.

Hope you find some useful info here.
LVL 11

Author Closing Comment

ID: 34184233
Good enough to get me going ... thx

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
This shares a stored procedure to retrieve permissions for a given user on the current database or across all databases on a server.
Viewers will learn how the fundamental information of how to create a table.
SQL Database Recovery Software repairs the MDF & NDF Files, corrupted due to hardware related issues or software related errors. Provides preview of recovered database objects and allows saving in either MSSQL, CSV, HTML or XLS format. Ensures recov…

588 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question