Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Reporting Services offers the <strong>rs.exe</strong> tool for this sort of thing.</p> <p>See <a href="http://technet.microsoft.com/en-us/library/ms162839.aspx" rel="nofollow">rs Utility (rs.exe) (SSRS)</a>.</p> <p>This utility takes a VB.NET script which contains code that interacts with a specified SSRS web service.</p> <p>You can add user-defined parameters to specify any other required variable.</p> <p>The main advantage with this is that <strong>rs.exe</strong> already has all the required references built in, so all you need to is specify the deployment location instead of creating a .NET project with WSDL references, etc.</p> <p>Disadvantage is that obviously this needs to be installed where you're deploying, i.e. typically run on a server with SSRS already installed. Also, it's VB.NET, which might not be to your taste. But the core functionality, i.e. connection to the web service, basic file operations are all natively available.</p> <p>You can also use these same sort of web service calls with Powershell.</p> <p>See <a href="http://www.sqlservercentral.com/blogs/dave_ballantynes_blog/2013/02/12/deploying-ssrs-artefacts-using-powershell-simply/" rel="nofollow">Deploying SSRS artefacts using Powershell ( Simply)</a>.</p> <p>This is another lightweight option, depends on how much you like working with Powershell, but all functionality, i.e. file manipulation and web service interaction can be achieved.</p> <p>I would look at <strong>rs.exe</strong> in the first instance.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload