ApexSQL Propagate

Learn more about minimum Windows permissions required to install and use ApexSQL Propagate on this link

Yes. Set the list of scripts in the Scripts pane and the list of databases in the Databases pane, and click the Execute button, from the Home tab

Yes. Click the New button in the List section under the Home tab, then choose the New script list option. If you want to reuse it, click the Open button, from the Lists section, and choose the Open script list option

Yes. Each script can be ordered by moving it up and down, depending on desired execution order, using the Move up/down buttons from the Script section in the Home tab

Yes. Click the Add database list button in the Databases section, under the Home tab and in the opened window you can add servers from which you can choose databases to create a list. When you want to reuse it, click the Open button, from the List section, and choose the Open database list option

Yes. Click the Combine script lists button from the List section, under the Home tab, load script lists on left and right side and move/copy scripts from side to side. Once the combining of scripts is finished, you can save the list as the currently loaded one or as a new list

No. But, the next version of ApexSQL Propagate will have support for Command Line Interface along with some other features and you can read more about it from here

ApexSQL Propagate is licensed per user as a part of the ApexSQL Fundamentals Toolkit for SQL Server bundle and requires activation

No, ApexSQL Propagate is fully functional during the 14 day trial period. After the trial period is over, you need to purchase the license to continue using it

ApexSQL Propagate supports SQL Server Express, Standard, and Enterprise editions

Yes. ApexSQL Propagate supports Azure SQL Database V12 and SQL Server on Amazon RDS

Yes. You can connect to any of SQL Server editions or Azure SQL Database server or SQL Server on Amazon RDS, and create a deployment list of databases by combining any of these servers

Yes. You can save the SQL Server instances, against which scripts will be executed, as Server lists

You can parse scripts prior to execution with a click on the Parse button from the Home tab

Yes. If an error is encountered during the script execution, you can see the execution results in the Result pane, along with the error message

You can choose one of the following options for the Error handling in the Options window, from the Home tab:

1. Continue execution
2. Skip for databases where errors occur
3. Stop for databases where errors occur
4. Stop execution

You can view the execution results by scripts or by databases

Yes. You can export your execution results in CSV and TXT file