|
|
You're in the
sql server reporting services
group:Sharing Datasources across reporting projects
sql server reporting services:
"solution". It allows for links on the Reports Server to each basic category of reports which is nice. The problem is that while developing, within the Visual Studio .Net IDE we need to add "shared" datasources to each project. (We have several copies of the same database (schema) on different servers that we wish to run the same reports against). When these projects are deployed the datasources wind up in each of the project's folders on the reports server. Thanks to some comments elsewhere on this site, I've managed to determine that we can create a Data sources folder on the server and "move" the deployed data sources to this folder, then manually link the deployed reports to those datasources. Is there a way to maintain one set of datasources, deploy them automatically to the purpose built folder for datasources, and have ALL reports use them
Yes I think so, thanks Teo.
If we redeploy the entire project, which does contain data sources, but those datasources have been moved, manually to a different location on the server (new folder) they won't be created in the folder, on the server for that report project? I'll try it. [quoted text, click to view] "Teo Lachev [MVP]" wrote:
> Stuart, > > I don't think you have to update the data source each time you deploy the > report. If OverwriteDataSources is False, the data source definition won't > be updated. This mode will allow you to use the Report Manager to link the > report to a "central" data source > > Is this what you are asking for? > > -- > Hope this helps. > > --------------------------------------------- > Teo Lachev, MVP [SQL Server], MCSD, MCT > Author: "Microsoft Reporting Services in Action" > Publisher website: http://www.manning.com/lachev > Buy it from Amazon.com: http://shrinkster.com/eq > Home page and blog: http://www.prologika.com/ > --------------------------------------------- > > "Stuart" <Stuart@discussions.microsoft.com> wrote in message > news:43EAFE72-138F-4EB7-8FBE-21DC165BC4E7@microsoft.com... > > I am deploying reports from multiple "reports projects" within a single > > "solution". It allows for links on the Reports Server to each basic > category > > of reports which is nice. > > The problem is that while developing, within the Visual Studio .Net IDE we > > need to add "shared" datasources to each project. (We have several copies > of > > the same database (schema) on different servers that we wish to run the > same > > reports against). > > When these projects are deployed the datasources wind up in each of the > > project's folders on the reports server. > > Thanks to some comments elsewhere on this site, I've managed to determine > > that we can create a Data sources folder on the server and "move" the > > deployed data sources to this folder, then manually link the deployed > reports > > to those datasources. > > > > Is there a way to maintain one set of datasources, deploy them > automatically > > to the purpose built folder for datasources, and have ALL reports use them > > once deployed, without manual intervention? > >
Stuart,
I don't think you have to update the data source each time you deploy the report. If OverwriteDataSources is False, the data source definition won't be updated. This mode will allow you to use the Report Manager to link the report to a "central" data source Is this what you are asking for? -- Hope this helps. --------------------------------------------- Teo Lachev, MVP [SQL Server], MCSD, MCT Author: "Microsoft Reporting Services in Action" Publisher website: http://www.manning.com/lachev Buy it from Amazon.com: http://shrinkster.com/eq Home page and blog: http://www.prologika.com/ --------------------------------------------- [quoted text, click to view] "Stuart" <Stuart@discussions.microsoft.com> wrote in message news:43EAFE72-138F-4EB7-8FBE-21DC165BC4E7@microsoft.com... > I am deploying reports from multiple "reports projects" within a single > "solution". It allows for links on the Reports Server to each basic category > of reports which is nice. > The problem is that while developing, within the Visual Studio .Net IDE we > need to add "shared" datasources to each project. (We have several copies of > the same database (schema) on different servers that we wish to run the same > reports against). > When these projects are deployed the datasources wind up in each of the > project's folders on the reports server. > Thanks to some comments elsewhere on this site, I've managed to determine > that we can create a Data sources folder on the server and "move" the > deployed data sources to this folder, then manually link the deployed reports > to those datasources. > > Is there a way to maintain one set of datasources, deploy them automatically > to the purpose built folder for datasources, and have ALL reports use them > once deployed, without manual intervention?
I find that this option only prevents overwriting existing shared data
sources, but it does not prevent writing existing shared data sources from a project's folder to the server. I recommend defining the data source for a report via the connection string properties (without using a shared data source) in addition to specifying "False" for the OverwriteDataSources option for the project. You'll notice that the report is pointed directly to the database through the connection string when you initially post a report. You'll have to manually change the report's data source to your shared location. Although you have to do this manually for each time you initially post you will not have to do it again since the project will not overwrite the data source property of the report on the server. [quoted text, click to view] "Teo Lachev [MVP]" <teo.lachev@nospam.prologika.com> wrote in message news:%23aPpIzFyEHA.4040@TK2MSFTNGP11.phx.gbl... > Stuart, > > I don't think you have to update the data source each time you deploy the > report. If OverwriteDataSources is False, the data source definition won't > be updated. This mode will allow you to use the Report Manager to link the > report to a "central" data source > > Is this what you are asking for? > > -- > Hope this helps. > > --------------------------------------------- > Teo Lachev, MVP [SQL Server], MCSD, MCT > Author: "Microsoft Reporting Services in Action" > Publisher website: http://www.manning.com/lachev > Buy it from Amazon.com: http://shrinkster.com/eq > Home page and blog: http://www.prologika.com/ > --------------------------------------------- > > "Stuart" <Stuart@discussions.microsoft.com> wrote in message > news:43EAFE72-138F-4EB7-8FBE-21DC165BC4E7@microsoft.com... >> I am deploying reports from multiple "reports projects" within a single >> "solution". It allows for links on the Reports Server to each basic > category >> of reports which is nice. >> The problem is that while developing, within the Visual Studio .Net IDE >> we >> need to add "shared" datasources to each project. (We have several copies > of >> the same database (schema) on different servers that we wish to run the > same >> reports against). >> When these projects are deployed the datasources wind up in each of the >> project's folders on the reports server. >> Thanks to some comments elsewhere on this site, I've managed to determine >> that we can create a Data sources folder on the server and "move" the >> deployed data sources to this folder, then manually link the deployed > reports >> to those datasources. >> >> Is there a way to maintain one set of datasources, deploy them > automatically >> to the purpose built folder for datasources, and have ALL reports use >> them >> once deployed, without manual intervention? > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |