Deployment of Reports and Data Sources

What is the best way to deploy reports to production considering the fact that different developers would be working on different reports and different data sources. Also consider that the data sources connect to local machines of the developers during report creation and a different database server on deployment.

One way is to use VS2005 to deploy it to production but I am not sure if that is the way to go?

Any ideas?

Thanks

I'd probably create an RSS script which will publish the report to the whatever server it needs to and then actually "fixes up" the report to point to a "production datasource" which already exists on the production box. This "production datasource" points to the correct database on the server.

Use the CreateReport() API to publish the report, and here's a quick sample on fixing up the datasource on a report:

DataSourceReference reference = new DataSourceReference();
DataSource[] dsarray = new DataSource[1];
DataSource ds = new DataSource();
reference.Reference = "/Data Sources/AdventureWorks";
ds.Item = (DataSourceReference)reference;
ds.Name = "AdventureWorks";
dsarray[0] = ds;
rs.SetItemDataSources("/AdventureWorks Sample Reports/Company Sales", dsarray)

It bascially sets the datasource of the Company Sales report to point to the AdventureWorks datasource int he /Data Sources folder.

The nice thing about this idea is that if you have only a few different databases to deal with, you could actually write the RSS script to that it acts on all reports in filesystem folder, and then does some thinking and points each report to the correct "production" data source during the "fix up" phase...

Deny an Application?

Hello everyone,

Is there a way to deny a specific application from connecting to SQL Server? There is an application some of my developers use that connects with Windows Authentication that I would like to block from my production server. I can't deny the user's logins because they need to be able to connect to the server from other applications.

Does anyone have any suggestions?

Thanks in advance,

Jarret

Hi,

are you using SQL Server 2k or 2k5 ? You have to keep in mind that application names although they are provided automatically by applications can be spoofed easily by manipulating the connectionstring, so I don′t know if this solution would be feasible for you in this case.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

Sorry, I am using SQL Server 2005.

I understand that an application name can be manipulated, but even if the application name is spoofed, I would be able to include the new name in my list of applications to deny. This is a third party tool, so I don't think my developers will be able to modify the connection string very easily. However, if they do change the application name, I would like to be able to block it as well.

Thanks,

Jarret

|||Hi,

there is no generic way, you will have to implement something like this AUDIT_LOGIN event triggering here:

http://www.sqlservercentral.com/columnists/FVandeputte/sqlserver2005logontriggers.asp

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de