March 29, 2007 at 11:49 am
First I would like to apologize if my question is answered else where, but I have been researching for a couple days now with little luck. My situation is as follows.
Our webapp is set up as like this, Server A is our web server (IIS), it houses the .Net code and the reports, also Server B is our SQL Server (Database and Reports), it only houses the report service and the data.
I'm developing on my own PC (lets call it C), I have SQL Server 2005 and Visual Studio 2005 installed. I want to be able to download the reports from Server A into my own computer so that I can edit them and test them locally before deployment, but I want to use live data from Server B and basically avoid setting up a report server and a copy of the database locally.
The problem is, I don't know how to go about this, if I start a report project from scratch I can connect to server B and execute queries with out a problem, but when I run the report it says it can't reach the reporting server.
If I take the reports straight from server A into my PC and run them, the same thing happens.
Basically I want to know what are the key points I should be checking in order to make this happen.
I'm kinda lost cause I'm on my own and it's the first time I had to use SQL Server Reporting Service, any guidance would be greatly appreciated.
March 29, 2007 at 11:55 am
I'm not sure if I'm following you completely, but I'll go over a few things off the top of my head.
1. The firewall needs to be setup to allow the IIS server to see the SQL Server box.
2. The credentials embedded into the datasource must give the necessary permissions on the tables, stored procs, etc. Whatever is needed for your reports to run. You having permissions on the necessary SQL Server objects isn't enough. The datasource must have them. This assumes you're not using trust permissions.
3. To download the reports, you can go into Report Manager, and click the "Edit" link on the report properties page for the given report. It will let you save it as an .rdl file.
4. I always recommend starting small. Make a single report that has a simple "Select * From sometablethatmydatasourcehaspermissionsto" as its datasource. Once that works, start adding until you hit roadblocks, and then come back for help.
March 29, 2007 at 12:35 pm
thanks for the tips 😀
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply