Running database script against multiple databases on a server
For example, on our server, we currently have over 400 event databases. We would need to copy and paste the line to call the execute function 400 times and change the database name on each line.
It would a great feature if SQL Studio could give us a list of all databases on the server we connect to (with a check box next to each one), with an option to "select all". It would then automatically execute the query against all checked databases.
This would save us a lot of time, and would mean your product has all the functionality of SSMS Tools Pack - a popular add-on for SSMS.
Andy Shellam
shared this idea
In version 6.0, there is now a possibility to select the ‘Run On Multiple Targets’ command from the popup menu of a SQL document.
Please also see the following article https://blog.devart.com/dbforge-studio-for-sql-server-is-ready-for-devops-automation.html#run-scripts
-
Kirk Wolak
commented
First, I don't see this option on ENT edition. Which is sad.
And I have a server that has multiple databases.Second, it would be far better, if we could create a "Connection group" where we select the DB's (even not on the same server), to run against.
So that I can do my DEV schema upgrades, then my STAGING, then my PRODUCTION...
-
Richard Bayliss
commented
This would be a great feature for us if it was in the MySQL version of the product.
-
Rob Hudson
commented
I have several hundred databases. This would be such a high value addition. It could be implemented similarly to TOAD's "Group Execute" feature.
Even better, if we could point it to an Azure SQL Failover Group, that would make it so we don't have to run scripts against each server and weed through the failures caused by the read-only replica databases.
-
Karl Rostock
commented
I agree this is a really important feature, at the moment I have 300+ databases which need to be migrated for each release of our software, being able to run a set of sql upgrade scripts against a list of databases would be a killer feature.
-
Nick A.
commented
Too fuzzy description. I guess a better description would be to somehow have the ability to execute a script in multiple databases (which could exist in one or multiple servers). Not a bad idea.
-
Maxim
commented
Produce ability to perform multiserver scripts (as it's done in SSMS)