Any efficient method available ?? 1

[swenri]

I've a question regarding Yukon (SS 2005) Reporting Services.

Is there an efficient scripting method to update the connection string for ALL reports that reside on a reporting/web server? (automating the process, rather than having to change the data source for each individual report that resides on that server).

All inputs are highly appreciated.

Thanks,

 

[onpnt]

Not that I know of but if you manage your data sources well the task should not be difficult and then it will of course filter down to all your objects on the instance


[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[nomadicalloy]

you can use shared datasource for all the reports, that is lot easier to manage.


My Programming Blog

http://www.xpherion.com/wp/?cat=2

 

[onpnt]

That's pretty much what I meant by managed data sources

Sorry I wasn't clear


[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[swenri]

So you mean that if have a shared datasource like for example TSAS_SDS.sds. where the datasource is

Data source =XXXDEVTEST1\REPORTING02;Initial Catalog = Portfolio.report

Now if for example the first Report1.rdl has been developed with a connection string as Data source =XXXDEVTEST1\REPORTING02;Initial Catalog = Portfolio.report

and another report has been developed with a connection string as Data source =XXXDEVTEST1\REPORTING02;Initial Catalog = Portfolio.Data

It should work when I deploy the reports on the server.(Report Manager)

Is that correct ? Thanks a lot once again.

 

[onpnt]

Yes. You simple are using one data source for several reports. I don't think out of dozens of reports in a group I have ever used more than 2 data sources. If you need to go to things like Oracle, DDB2 etc... you do that on the database level and not in the data source so its pretty straight forward.

If you're infrustructure is setup with reporting services sitting on its own server and database instance then you should never (IMO) connect to anything but that instance. Then control outside resource connectivity through the instance. Make sense?


[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[ceh4702]

Might be nice if you could store the string in a file and just copy it into the code. That way it would be updateable. Even mainframes had copybooks.

Are all your reports standardized?

We just did a conversion on our ERP to a new version on a new server. So we renamed the old server and the new server so it actually is the same source on all the setups.

If you do not like my post feel free to point out your opinion or my errors.