I run a small reporting team / business intelligence team that uses the full Microsoft stack of tools - ie, SSRS, SSIS and SSAS. Over time, most of the team have cultivated their own idiosyncratic workflows. For the most part, since we typically work autonomously, this hasn't been a major issue as long as basic good practices are maintained. But we are increasingly working on larger, collaborative projects and I want the team to cultivate some standardised approaches.To that end, I'd really appreciate any thoughts on some of the following issues;* How do you structure your reporting services projects? eg, do you create a new project for each... "group" of reports? If so, how do you group reports?* How do you handle versioning and source control? Do you use a version control system? If so, which one?* How you move from development to production? In particular, how does this work if you are using a version control system?* What do you use for documentation? What about report meta data - eg, do you document report "owners"? Whenever I try to google for "best practices" and "reporting services", I tend to get results around deployment of the infrastructure. I'm struggling to find resources on best practices for actually using the products.
↧