Best Practices for RS and VSS

We are starting to use VSS2005 for storing projects and rdl files. We are
mainly using it for the versioning capabilities in VSS. Does anyone have any
tips for best practices on how to utilize Visual Studio 2005 and VSS 2005?
IF anyone has a link or two to sites that go over this topic that would be
helpful too.
The problem have had so far is trying to check out the rdl files through VSS
and then open them in Visual Sutdio to edit them. Whenever I have checked
out a file in VSS and then opened the file using the options in VSS to get to
Visual Studio (devenv) I either get a message stating that the carriage
return is messd up in the file or it opens the rdl code... not the designer
window.
If I check out the file in VSS and then open the file through Visual Studio
without using VSS to get to Visual Studio, everything works fine, but that
just seems a little too manual. Thanks in advacne for your help.On Jul 5, 4:50 pm, bsod55 <bso...@.discussions.microsoft.com> wrote:
> We are starting to use VSS2005 for storing projects and rdl files. We are
> mainly using it for the versioning capabilities in VSS. Does anyone have any
> tips for best practices on how to utilize Visual Studio 2005 and VSS 2005?
> IF anyone has a link or two to sites that go over this topic that would be
> helpful too.
> The problem have had so far is trying to check out the rdl files through VSS
> and then open them in Visual Sutdio to edit them. Whenever I have checked
> out a file in VSS and then opened the file using the options in VSS to get to
> Visual Studio (devenv) I either get a message stating that the carriage
> return is messd up in the file or it opens the rdl code... not the designer
> window.
> If I check out the file in VSS and then open the file through Visual Studio
> without using VSS to get to Visual Studio, everything works fine, but that
> just seems a little too manual. Thanks in advacne for your help.
This is a kind-of undocumented territory. This link might be of
assistance.
http://geekswithblogs.net/VROD/archive/2006/11/22/97817.aspx
Also, if VSS 2005 is not suitable, you could try Subversion or some
other Source Control software.
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Best Practice promotion of RDL from Dev to Test then onto Prod

I have been tasked with creating our promotion procedures for all
reports in Reporting Services. Can anyone give me any tips or point
me to any references that will help me with this.
Ideally I would develop the report in a dev environment against dev
data.
It would go through our quality assurance process against test data
where both the data and report layout would be verified.
Then promoted to production.
Any help is most appreciated.
Thanks.I have also been working on the deployment issue and do not have a good
process. I would also like to go this on a single SQL server. Any thoughts?
"Brian H" wrote:
> I have been tasked with creating our promotion procedures for all
> reports in Reporting Services. Can anyone give me any tips or point
> me to any references that will help me with this.
> Ideally I would develop the report in a dev environment against dev
> data.
> It would go through our quality assurance process against test data
> where both the data and report layout would be verified.
> Then promoted to production.
> Any help is most appreciated.
> Thanks.
>|||Where I work, we have seperate Dev, Staging, and Production
environments for SQL as well as the Sql Reporting servers.
Deployment consists of simply publishing Stored Procedures and RDS, and
RDL files in each environment, testing, then promoting to the next
until you reach Production.
Was there something more specific you were looking for? Do you have
any hardware constraints that might factor-in?
Regarding using a single Sql Server, I'm not entirely sure how you
might do this, since you still need a seperate ReportServer &
ReportServerTempDB instance for each environment. There may be a place
to reconfigre Sql Reporting to use different DB names so that the
different DB instances can be referenced.
Beware that all DB instances on a server share the same MASTER
database. This can be an issue when applying Service Packs, because
deployment to one target DB will still affect all DB instances via the
common MASTER database as occurs in SP-1. However, you may be able to
work around this by creating multiple database Instances on the same
server. I'm not a DBA, but I think they will have seperate MASTER
databases in that case.
I hope this helps a bit,
Lance Hunt
http://weblogs.asp.net/lhunt/