How do I get Visual Studio to open a deployed report?

Greetings,

I have a report that was previously deployed to a reporting services host (running Reporting Services 2005 SP2) and I'm running the version of Visual Studio that came with reporting services on the same reporting serviceshost. The deployed report was never opened on this particular server, so it doesn't appear in the recent files list. Is there a trick to open a deployed report in all of Visual Studio's report editing glory? Visual Studio has a File Open option to open an analysis services database, a project, or a file. A "deployed report" seems to be none of these options since it's an RDL file stored somewhere that IIS can find it. I know that I can use Report Manager and export the RDL for the report and then edit that RDL file in Visual Studio, but doing that appears to disable all of Visual Studio's report editing features (ie it works no better than notepad). What's the trick to get Visual Studio to open the deployed report and allow all of it's editing tools to work properly and then save the updated report back to the reporting services server?

Thanks,

Ron

In report manager, go to the report properties.

there is a button in there 'save/edit' or similar

you can then save the file locally and open it in vs.net

NB don't forget 2000 rdl files will be automatically upgraded to 2005

How do I disable transaction logging in a stored procedure?

Greetings,

I would like to turn off transaction logging for a long-running stored procedure. It is doing some one-shot utility work in a temporary table. If the stored procedure fails then I'll delete all the rows in the table.

Is is possible to turn off (or at least minimize) the logging for a single stored procedure? I'm looking at this from a performance perspective, thinking that doing no logging will speed things up a bit. The stored procedure will potentially update hundreds of thousands rows.

Am I on the right track or barking up the wrong tree?

Thanks,

BCB

hello,

everything that happens in the database are entered into the transaction log

when you are in the full recovery.

you may only choose any of the three recovery model to handle the log size

1. simple

2. bulk logged

3. fully logged

you can deal with the logs only as a part of your db maintenance procedure.

thanks,

joey