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 |
|
BitShift
Yak Posting Veteran
98 Posts |
 Posted - 2007-02-01 : 16:21:46
|
| We are planning on using 2005 report services. Im wondering how I can feed reports to my asp.net web application that resides on a different machine.The scenario is:user -> IIS web app -> report on sqlI guess the real question at this point for me, is if I have reports - can I have them cached in pdf format and then how are they accessed with a url ? |
|
|
snSQL
Master Smack Fu Yak Hacker
1837 Posts |
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2007-02-02 : 16:43:31
|
| I do have a question. I created simple reports to read straight out of the table and display the results. The reports are visible to me(as my domain account has the SA privileges) or from the server directly. But when I have a user look at it, he gets an error message. Permission denied. There was some mention about it in the reporting service BOL. It said to give certain permissions to the user on reportseverdatbase, reportservertempdb, msdb and master databases. I did exactly what is asked but still the same problem, any body know how we can solve this issue? |
 |
|
|
jhermiz
3564 Posts |
Posted - 2007-02-07 : 12:09:20
|
quote:
Originally posted by pareshmotiwala
I do have a question. I created simple reports to read straight out of the table and display the results. The reports are visible to me(as my domain account has the SA privileges) or from the server directly. But when I have a user look at it, he gets an error message. Permission denied. There was some mention about it in the reporting service BOL. It said to give certain permissions to the user on reportseverdatbase, reportservertempdb, msdb and master databases. I did exactly what is asked but still the same problem, any body know how we can solve this issue?
Bad practice to write reports using the SA account. Its also very bad practice to create reports directly from tables. You should use stored procedures which add a level a security to access the data.What you want to do is create a role I usually create a role called db_reporter. Within that role you add a SQL Server user called say "rs". You give rights to that user to any stored procedure that is used to access the data. Then all users go through this role because that user is set as the reports data source user.The reason you are having issues is you do not associate rights to your data, you simply use SA. When you create a shared data source to use it asks you for a user name and password. Please don't tell me you are using SA there with a blank password :(.
Keeping the web experience alive -- [url]http://www.web-impulse.com[/url]RS Blog -- [url]http://weblogs.sqlteam.com/jhermiz[/url] |
|
|
|
|
|
|
|
|
report web service and access from another web app