Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jassie
Constraint Violating Yak Guru
332 Posts |
 Posted - 2011-05-07 : 18:20:45
|
| I have the following questions to ask about sql server 2008 r2 standard edition:1. At work, a fellow co-worker says the SSRS reports lose the data source connection strings and the user name and pawwrods to some when the SSRS 2008 r2 report is setup. Is there a way to prevent this from occuring?2. Is there a way to keep users from seeing all the reports that can be executed from running? Basically some of the people in the IT department that have the same access level, said they could not see some reports on the Microsft version of the sql server web service? If this is true, how can you prevent this from occuring? |
|
|
ajthepoolman
Constraint Violating Yak Guru
384 Posts |
Posted - 2011-05-09 : 09:15:27
|
| I think I can help a little.1. When I read this I assumed that the issue is that a report is developed, then moved to a production environment, at that point the connection string information is lost. That has been my experience as well. Even if the settings from development to test to production were all the same, it still has to be reset when the report is uploaded. I do not know of a way to prevent it.2. To get around permission issues, we used Active Directory groups and then locked folders down based on Active Directory settings. It is kind of a pain, but it is a good way to lock people down.Hey, it compiles. |
 |
|
|
jassie
Constraint Violating Yak Guru
332 Posts |
Posted - 2011-05-10 : 21:28:13
|
| Thanks! this helps! |
|
|
|
|
|
|
ssrs 2008 r2 process options