I am trying to implement a system we had at another place of work where I have a master/shell report that sets permissions for users for reports that will be included as subreports. I figured I can grab the username and give them a group identifier that will restrict parameter visiblity and such that whoever is logged in can only see the information that pertains to them or their team or their projects.
Right now I have multiple copies of the same reports based on if they are team leaders, project managers or executive staff and I'm having to try and go around to each and make changes and its not effecient so I want one master report. In JSP we had headers that defined what people could see. I'd like something like that. Executive should have free access to change parameters but others should only see their stuff.
Our database/sharepoint was setup by outsiders and within we are not well versed enough to implement some of the features that would make my life easier such as stored procedures and SSAS and since I'm working with LIVE data (no sandbox yet) what I do now has to be limited until we have a setup where I can experiment without fear of destroying what is already in place. So I wanted to keep it to everything I can do in Bids 2008.
I've read about using parameters to store UserID but I thought a variable might be better. Any suggestion on the method I should follow? I don't need how-to's as much as 'this is the systematic approach to follow' suggestions. Any help is greatly appreciated!!!!
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied?
You can use SQL Server Initialize from Backup…
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…