We do what Jasper is suggesting.
We create a data source (maybe called Prod) in the project. The first time
we deploy, we go into report manager and change the connection information to
whatever it needs to be. Since redeployment does NOT change the connection (
unless you change the config), everything works fine.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
[quoted text, click to view] "Mike Kelly" wrote:
> Hi. I love the time-saving features of Reporting Services. I desing my report
> in VS2005. Then deploy them to my QA server and, when that passes testing,
> put it into my PROD environment. That all works very nicely.
>
> I have defined 2 data sources, one for QA and one for PROD. What gets to me
> is that after deploying to QA I have to go into Report Manager and select the
> QA data source for each of my reports. Then, once deployed to PROD I have to
> do the same. This becomes a major headache when I have to make many small
> changes to a report and repeat the process each time.
>
> Is there a way to specify an alias of some form that can point to my
> development server data source when on my machine, and to the appropriate
> databases when on QA and PROD?
>
Thanks Jasper and Wayne.
I am using shared data sources, but incorrectly. I was deploying them each
time. But was blind as to their inteded use. The word "Shared" threw me off
course. Now I see. I'll replace the two I was using (one for test and one for
prod) with a single one (since I only have a single database) and change the
definition for that one depeding on the environment it is running in. So
simple, once you get it!
[quoted text, click to view] "Wayne Snyder" wrote:
> We do what Jasper is suggesting.
> We create a data source (maybe called Prod) in the project. The first time
> we deploy, we go into report manager and change the connection information to
> whatever it needs to be. Since redeployment does NOT change the connection (
> unless you change the config), everything works fine.
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
>
> I support the Professional Association for SQL Server ( PASS) and it''s
> community of SQL Professionals.
>
>
> "Mike Kelly" wrote:
>
> > Hi. I love the time-saving features of Reporting Services. I desing my report
> > in VS2005. Then deploy them to my QA server and, when that passes testing,
> > put it into my PROD environment. That all works very nicely.
> >
> > I have defined 2 data sources, one for QA and one for PROD. What gets to me
> > is that after deploying to QA I have to go into Report Manager and select the
> > QA data source for each of my reports. Then, once deployed to PROD I have to
> > do the same. This becomes a major headache when I have to make many small
> > changes to a report and repeat the process each time.
> >
> > Is there a way to specify an alias of some form that can point to my
> > development server data source when on my machine, and to the appropriate
> > databases when on QA and PROD?
> >
Don't see what you're looking for? Try a search.
