Multi-team and Multi-Server deployment environment issue

ACK!
So, here I am at my new job, thinking I'm learning RS because they have it
deployed in their environment, only to find out that I'm a member of one of
the teams *expected* to deploy it in the near future...
Due to SOX (Sarbane-Oxley) and other issues, we're going to have 3 servers:
Development, QC and Production.
There are also three teams: Development, QC and Production. I'm a member of
the Dev team. We have to figure out a way to deploy the Reports to the Dev
server for development, then allow the QC team to deploy the reports from the
Dev server to the QC server for testing, and finally to allow the Prod team
to deploy the reports from the QC server to the Production server without the
use of the Visual Studio .Net Deployment tool (since the Production team
doesn't have access, and likely the QC team doesn't either).
One of my co-workers is thinking he'll have to write a whole new app to
import the reports. The other option we can think of is the RS.exe script,
but that will require someone managing that script full time.
Does anyone have any other thoughts?
Thanks,
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)You may want to check the following tool courtesy of Jasper Smith:
http://www.sqldbatips.com/showarticle.asp?ID=62
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Catadmin" <goldpetalgraphics@.yahoo.com> wrote in message
news:7AD0D78A-682E-4904-8CF2-EA6AC04F6F7A@.microsoft.com...
> ACK!
> So, here I am at my new job, thinking I'm learning RS because they have it
> deployed in their environment, only to find out that I'm a member of one
> of
> the teams *expected* to deploy it in the near future...
> Due to SOX (Sarbane-Oxley) and other issues, we're going to have 3
> servers:
> Development, QC and Production.
> There are also three teams: Development, QC and Production. I'm a member
> of
> the Dev team. We have to figure out a way to deploy the Reports to the
> Dev
> server for development, then allow the QC team to deploy the reports from
> the
> Dev server to the QC server for testing, and finally to allow the Prod
> team
> to deploy the reports from the QC server to the Production server without
> the
> use of the Visual Studio .Net Deployment tool (since the Production team
> doesn't have access, and likely the QC team doesn't either).
> One of my co-workers is thinking he'll have to write a whole new app to
> import the reports. The other option we can think of is the RS.exe
> script,
> but that will require someone managing that script full time.
> Does anyone have any other thoughts?
> Thanks,
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the
> back?
> @.=)|||Thank you, Robert. I greatly appreciate the link.
Catadmin
--
MCDBA, MCSA
"When I get back, you're going to argue with me about the things that I want
to argue about!" Josh Lyman, The West Wing
"Robert Bruckner [MSFT]" wrote:
> You may want to check the following tool courtesy of Jasper Smith:
> http://www.sqldbatips.com/showarticle.asp?ID=62
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Catadmin" <goldpetalgraphics@.yahoo.com> wrote in message
> news:7AD0D78A-682E-4904-8CF2-EA6AC04F6F7A@.microsoft.com...
> > ACK!
> >
> > So, here I am at my new job, thinking I'm learning RS because they have it
> > deployed in their environment, only to find out that I'm a member of one
> > of
> > the teams *expected* to deploy it in the near future...
> >
> > Due to SOX (Sarbane-Oxley) and other issues, we're going to have 3
> > servers:
> > Development, QC and Production.
> >
> > There are also three teams: Development, QC and Production. I'm a member
> > of
> > the Dev team. We have to figure out a way to deploy the Reports to the
> > Dev
> > server for development, then allow the QC team to deploy the reports from
> > the
> > Dev server to the QC server for testing, and finally to allow the Prod
> > team
> > to deploy the reports from the QC server to the Production server without
> > the
> > use of the Visual Studio .Net Deployment tool (since the Production team
> > doesn't have access, and likely the QC team doesn't either).
> >
> > One of my co-workers is thinking he'll have to write a whole new app to
> > import the reports. The other option we can think of is the RS.exe
> > script,
> > but that will require someone managing that script full time.
> >
> > Does anyone have any other thoughts?
> >
> > Thanks,
> >
> > Catadmin
> > --
> > MCDBA, MCSA
> > Random Thoughts: If a person is Microsoft Certified, does that mean that
> > Microsoft pays the bills for the funny white jackets that tie in the
> > back?
> > @.=)
>
>sql