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 |
|
Maxer
Yak Posting Veteran
51 Posts |
 Posted - 2008-01-17 : 09:15:43
|
| I have a question about assigning permissions for SQL Server 05's reporting services.We have an outside party that needs access to run reports on our reporting services server.However, I want to make sure they can't see anything else on our database server. (They need logins to connect to the server and then at that point in reporting services I only grant them access to a single folder that has the reports they need in the web interface).I just want to be sure they can't poke around and see anything else in the server.What would be the best way to handle that?Just create their logins and grant them connect / login permissions only? Let them fall into the PUBLIC role?Should I create a new role just for them? |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-19 : 23:25:55
|
| Don't grant them more permission than needed, and don't tell them sql server name. |
 |
|
|
mdubey
Posting Yak Master
133 Posts |
Posted - 2008-05-26 : 21:28:59
|
| As I know about reporting services, You do not have to give SQL server DB name to the third party vendor as well.You need to give only Read permission on the reporting DB.ManojMCP, MCTS |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2008-05-26 : 21:47:46
|
| This is getting to be spam.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
How to assign permissions properly- 3rd parties