putting subscriptions and other SSRS things in SourceSafe?

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?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?|||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?
"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?
>
>

Publishing from Oracle to Sql Server 2005

HI guys,

Am trying to do the above. Managed to configured the distributer. However, while trying to configure my oracle publisher, it failed as follows:

====================================================
Creating Publication

- Creating Publication 'oraTest' (Success)
* SQL Server created publication 'oraTest'.

- Adding article 1 of 1 (Error)
Messages
* SQL Server Management Studio could not create article 'USERS'. (New Publication Wizard)

ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Objects cannot be published from the publisher login schema [SCOTT].
Changed database context to 'distribution'. (Microsoft SQL Server, Error: 20802)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1187&EvtSrc=MSSQLServer&EvtID=20802&LinkId=20476

======================================================

As u guys can see, the publisher was created smoothly. It is the adding of the article, ie. my oracle table. I have ran the permission script as instructed in the BOL.

Wat am I missing? Can anyone pls help?

Thanks!

Cheers,
Kevin
-

Hi Kevin,

Can you please make sure that you have granted read permissions on the tables to the Oracle user account for managing Oracle publisher?|||Kevin -

The reason that you get this message is that you tried to publish tables that were in the schema account that you provided for replication. This is not supported since the replication account in Oracle is used strictly for supporting replication. As Mahesh mentions above, you just need to grant select on your tables (which shouldn't be owned by the replication user) to the replication user you created.

Matt Hollingsworth
Program Manager

Publish A Report Services Report to SharePoint

OK... I'm running out of things to try.

I have SQL Server 2005 SP2 installed and Reporting Services Addin configured. I am trying to publish a report from BIDS to SharePoint... but a box continues to pop up asking me for credencials.

What am I doing wrong? I have reviewed all the web.config files as per an earlier post referenced, but I only see one entry in the config file for the location tag. However, I did see this tag in two config files... not certain if that is something I should be concerned with?

I'd really like to just get a sample report up on the Sharepoint Server so I can move forward.

Can anyone help?

You can always just upload the .RDL file directly into SharePoint using the SharePoint web UI. When RS integrates with SharePoint, we tell SharePoint to handle .RDL files as Report Server items, and it doesn't really matter whether they get into SharePoint through Report Designer, or through SharePoint web UI.

I'm afraid I can't help with the Report Designer issue. I'll pass this on to someone who might know about it.

|||Please check Inetpub\wwwroot\wss\VirtualDirectories\80\web.config|||

What am I looking for when I go to Inetpub\wwwroot\wss\VirtualDirectories\80\web.config?

It does have one entry for location path=" _vti_bin...." as previously mentioned, a number of the web config files have this entry in it... but only once per file.

And just to clarify... I am using BIDS trying to deploy the report. The version of Visual Studio is: 8.0.50727.42.

|||I did that and surprisingly it worked... how does the report connect to the database? I did not upload or create a datasource? Well... actually I had manually created one in SharePoint in another library, but subsequently deleted it. The report still runs?|||Actually... I'll answer my own question... the first report used a custom data source... so that is why it worked. The second used a shared data source... it failed until I created the shared datasource|||

I've been running into this, too. Brian Welcker's blog solved it.

http://blogs.msdn.com/bimusings/archive/2007/02/07/reporting-services-login-dialog-appears-when-deploying-to-moss-wss.aspx

publication database not listed

When I create new subscription there is nothing listed under SQL Server.
I configured Server for replication, then published myDatabase.
Then I wanted to subscribe to this database, but couldn't -
I ckick on Server's Name under tree and tha's it - nothing is shown under it
to pick from.
There is following message in event log:
The replication agent is not registered properly. Rerun SQL Server setup.
We have SQL Server 2000 with spk3 installed.
We have production databases on it and can not rerun installation.
Is there anyway to reconfigure the server or do something else?
Any suggestions will be appreciated.
Thanks.
Can you tell me exactly the steps you take to get this? IE, right click on
the publication, push new subscription, etc.
Then while you are doing this run profiler and ensure you capture all
errors. Then post the results back here.
There have been cases where replication stored procedures go missing. It is
unclear whether these procs where ever installed or if they were deleted
somehow.
Can you run the following in your master database?
select count(*) from sysobjects where type ='p' and report back here with
the count!
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Alan" <Alan@.discussions.microsoft.com> wrote in message
news:823A7863-6166-4164-B02E-F317688CBA9D@.microsoft.com...
> When I create new subscription there is nothing listed under SQL Server.
> I configured Server for replication, then published myDatabase.
> Then I wanted to subscribe to this database, but couldn't -
> I ckick on Server's Name under tree and tha's it - nothing is shown under
it
> to pick from.
> There is following message in event log:
> The replication agent is not registered properly. Rerun SQL Server setup.
> We have SQL Server 2000 with spk3 installed.
> We have production databases on it and can not rerun installation.
> Is there anyway to reconfigure the server or do something else?
> Any suggestions will be appreciated.
> Thanks.