Daniel-
Sorry I wasn't clear. Our intention isn't to use the XML files that we
version in SourceSafe in order to ever restore or write anything back to the
database... it's just for versioning purposes... as in "what changed when we
deployed the Apr 12 release?" and doing a diff on the March and the April 12
file versions would tell us that. If we ever had to go back... or if anyone
accidentally deleted a report (which kills all its subscriptions)... we could
open up the XML and use it as a guide for reconstructing the recipients and
query of the data driven subscription... manually and through the Report
Manager interface.
So I take it nobody has any good suggestions for third-party software or
good processes for handling this? Does anyone else have similar needs?
[quoted text, click to view] "Daniel Reib (MSFT)" wrote:
> You have to be careful with messing with rows of the database. We may
> change the database at anytime and when you try and return it to the DB it
> might not be the same anymore.
>
> You could extract the information via the SOAP interface and then create a
> script that would create the subscriptions. You could then save off these
> scripts and use them against any RS server.
>
> Also, is there a reason that backing up the DB is not good enough?
>
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "FurmanGG" <FurmanGG@discussions.microsoft.com> wrote in message
> news:E05AB1EE-5671-4106-885D-627DDB28293A@microsoft.com...
> > There are things configured/setup in Report Manager that we would like to
> > version in Visual SourceSafe... the setup of data-driven subscriptions,
> > for
> > instance. Has anyone done this? Does anyone know of a third-party product
> > that assists with this?
> >
> > I'm currently thinking of writing some code to take a
> > ReportServer.dbo.Subscriptions record and format it as an XML file that we
> > can put in VSS. Can anyone think up a better idea?
>
>
