Click here to monitor SSC

Project Manager - Red Gate Software

Single-click script execution on multiple SQL Servers

Published 21 November 2007 9:28 am

New SQL Multi Script tool for DBAs

After talking with DBAs who look after multiple SQL Servers, it was clear that one of their most common tasks is to deploy scripts, query databases and collect aggregated results across their enterprise. With the use of SQL Server client-side tools, this task is nowhere near as straightforward as it could be.

The DBA needs a concentrated period of time to steadily repeat the execution of the same script or a set of scripts against multiple databases. This common task uses up valuable time that – time that DBAs could proiftably on more problem-soloving tasks.

It was with the busy DBA in mind that we developed SQL Multi Script. The tool is easily installed, and you only need a few minutes to learn how to create or open existing SQL scripts, edit them, parse them, execute them and browse the aggregated results returned. What’s more, this can all be done from a single interface. One mouse click at the top of the interface will let you execute all your selected scripts in one go.

A number of features are also included in SQL Multi Script to make life a whole lot easier for the DBA when scripts need to be deployed across different servers. Queries can be cancelled and SQL Multi Script can also be set to four different failure behaviors, should an error occur during deployment. Lists of databases on multiple SQL Servers can be customized and saved, so that it’s easy to execute a set of scripts against a particular set of SQL Servers in the future. You can also configure the number of databases against which to run scripts in parallel. Once the results of queries are returned, the results can be saved as .csv or .txt files for use in an external application.

The reactions of DBAs so far have shown that we’ve achieved what we set out to do. One DBA, with more than 50 SQL Server instances to manage, describes SQL Multi Script as having ‘the potential to be a godsend’.

Now that I’ve whetted your appetite, you can watch a demo, read customer testimonials and download a free 14-day trial (the trial enables you to execute scripts against an unlimited number of servers) for SQL Multi Script from the product pages.

We would also welcome your feedback on SQL Multi Script, so please feel free to post your comments on the  SQL Multi Script forum.

7 Responses to “Single-click script execution on multiple SQL Servers”

  1. PollusB says:

    I have a free alternative to this product ! It’s all made of DOS Command prompt batch code. And it’s also easy to integrate to SQL IDE like QA in the tool menu. Solution is simple because it uses a FOR loop with OSQL command. You can pass a filename or a command.

    For aggregation, I use BCP to download the result of a command from every servers down to files then I piped them in one CSV file which I open in Excel.

    If you would like to get the files, reply to me

  2. Helen Joyce says:

    Hi PollusB

    Thanks for posting and making the point that there are alternatives for solving the problem of executing lots of scripts against lots of servers.

    The solution in your post uses a chain of free products where you can use a DOS batch file to execute a script multiple times using OSQL – this would be the equivalent of SQL Multi Script serial mode. The script has to insert the results as a temporary table in the database. The results are then exported using bulk copy and concatenated into a CVS file. Although your solution is a viable alternative, I think there are a number of advantages and additional features in SQL Multi Script to the solution you describe in your post. With SQL Multi Script:

    • Scripts can be executed on databases in parallel – saving you time when querying many databases (on many servers)
    • An intuitive GUI lets you easily organize your scripts and databases
    • Sets of scripts can be executed
    • You can save your own database distribution lists of commonly used databases and servers
    • Error handling is configurable and any errors are reported in the GUI
    • Messages are collated
    • SQL Multi Script will intelligently combine data with differing schema

    With this kind of functionality, our aim for SQL Multi Script has always been to provide a more intuitive, faster and easier solution to script execution across multiple SQL Servers.

    Kind regards,

  3. PollusB says:

    Now that I see the differences, you make your product more appealing.


  4. Matt H says:


    Can you provide some more detail on your last bullet point? What do you mean by intelligently combining data with different schema?


  5. Helen Joyce says:

    Hi Matt.

    I mean it will return an aggregated results set where the same query is executed against more than one database and even if the data returns different columns it will still display it in one table.

  6. maverom says:

    Hello Helen,

    I want to congrats the team for these product.
    I suggest an improvement: combining data is a good feature, but it will be better if the differences regarding schema would be shown (in “Results” tab) with highlighted cells with other background color, not with NULL values (because NULL could be a value for an existing column).
    Maybe in the next version you will have implement this. By the way, when we will see the next version? The last was in 2007. (!?)

Leave a Reply

Blog archive