SQL Server execute scripts - multiple scripts, multiple databases

You launch SQL Server Management Studio – open script #1 and execute it against database 1 on SQL Server 1, then execute it against database 1 on SQL Server 2… then open t-sql script #2 and execute it against database 1 on SQL Server 1 etc… what a painful process, you dread the day you have to go through this (sometimes that is everyday). What a waste of resources too – a $100K database administrator spending hours executing scripts on tenths of server!

No more! You can now use Script Executor to take care of this job for you. One time only, you will go through a simple, and may I suggest fun, process of organizing your scripts into virtual containers and your databases into groups; then, map those script containers to the database groups; set an order of precedence if you need to and voila you have a package that you can now execute with a single click; or, you can even schedule it to run before you even make it to the office.

Script Executor will execute each script in the order you have defined against each database based on the mappings you have defined and once completed it will generate a comprehensive report allowing you to see how the script execution went on each target and also easily “flip through” the result sets that those scripts may generate.

Deploying (executing) multiple scripts against multiple SQL Server databases has never been easier.

You can download a free trial version of Script Executor from: http://www.xsql.com/download/script_executor/

A free community edition of Script Executor with limited functionality is also available: http://www.xsql.com/download/script_executor/

Applies to:

• SQL Server execute t-sql scripts
• SQL Server execute multiple scripts
• SQL Server deploy scripts to multiple databases
• SQL Server package t-sql scripts
• SQL Server run multiple scripts

Best way to execute t-sql scripts

Whether you need to deploy / execute multiple t-sql scripts to hundreds of your clients or to hundreds of your enterprise servers Script Executor is your best bet. For starters, it supports SQL Server 2000/2005/2008, MySql 5.0 and higher, DB2 9.0 and SQL Server Compact 3.5. It allows you to quickly organize your scripts into virtual script containers and organize your servers into virtual server groups. You can then map the script containers to the server groups, define execution precedence if necessary, and finally just deploy them OR package the scripts into an executable. Imagine, instead of sending your clients t-sql scripts and telling them to download and install Sql Server Management Studio so that they can run your scripts you can just send them an executable file that anyone can run - no that's easy!

Executing multiple Sql Scripts

If you work with SQL Server and especially if your job includes DBA tasks it is very likely that you have run into situations when you had to take a bunch of scripts (maybe tenths of them and maybe hundreds) and execute them in a certain order one after the other against a database. It is a tedious task to say the least. Now imagine if you had to do the same thing for 10 servers or 100 servers then you are really in trouble - there comes a point when it will be more efficient for you to sit down and write an application that will help you automate the process then do this job even once.

Well, you don't have to go through that annoying process anymore - with Script Executor, in just minutes, you can configure a highly complex scenario involving hundreds of scripts and tenths of target servers after which your highly complex deployment will require just one click or even none if you use the command line utility.

Download Script Executor now and see for yourself why we are so excited about it!