I have a bunch of SQL Servers registered within my SSMS, lots of different SQL versions, editions and DB compatibilities. I want to check out if **any** of those servers have **any** of the [sp_Blitz](https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit) or [sp_WhoIsActive](http://whoisactive.com) stored procedures installed, and which versions they are. I know I can **right-click** on my **Registered Servers group** and open **one** query window that connects to **all** the servers in the group, but is there a reliable way to check which SProcs and versions I have?

We set up multi-server administration to create a job on the master which are executed on target servers, and we had this issue because the target server was shut down after a virus attack and we set up a new SQL Server with the same name and restore all data including the master database on the new server, all the job is functioning as it used to be but now the issue happened when I am trying to update them, I can update the job at master SQL Server to change the schedule however the target server is not updating since it stopped polling after the original old server shutdown because of the virus attack, Currently, the new SQL Server Agent is not showing (tsx) I tried to force poll but it's not working. my trial to add it as target server is not working with a duplicate error too. Also, my trial to update the job at the target server is not possible since it's not active to even update Please advise how can I reconnect this master and target server with out losing all jobs.

We have a software package where the db are running sql 2022. I have many regions. Subdomains for each company that we work with. However the software and dbs are identical in structure. Is there a way that if I update 1 regions db I can update the other 20 simultaneously? Or is there a management software that can do this?

We are looking to shard our application, so that each customer has their own database. The data contents of all databases are different, but the structure is the same for all customers. Imagine there are 2 million customers. How do we update 2 million databases to: 1. Create, modify or eliminate columns. 2. Create, modify or eliminate tables. How do we do this across millions of databases across dozens of instances? We know how to do it manually, but how can this process be automated? So that we just modify one instance, and that propagates to all customers. Remember each customer has completely different data in each database. Thanks!

SQL Server 2019 MSX/TSX environment. TSX servers are clustered instances. MSX is not. There is a SQL integration service on each of the nodes in the cluster. I create a maintenance plan on the MSX and when i try to push it to the TSX i get this error: >Message Failed to import Maintenance Plan 'MaintenancePlanMSA' from MSX: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve data for this request. ---> Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Parameter 0 is incorrect for this statement. The statement has been terminated. at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException) at Microsoft.SqlServer.Management.Common.ServerConnection.GetExecuteReader(SqlCommand command) --- End of inner exception stack trace --- at Microsoft.SqlServer.Management.Common.ServerConnection.GetExecuteReader(SqlCommand command) at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataReader(String query, SqlCommand& command) at Microsoft.SqlServer.Management.Smo.DataProvider.SetConnectionAndQuery(ExecuteSql execSql, String query) at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataProvider(StringCollection query, Object con, StatementBuilder sb, RetriveMode rm) at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillData(ResultType resultType, StringCollection sql, Object connectionInfo, StatementBuilder sb) at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillDataWithUseFailure(SqlEnumResult sqlresult, ResultType resultType) at Microsoft.SqlServer.Management.Smo.SqlObjectBase.BuildResult(EnumResult result) at Microsoft.SqlServer.Management.Smo.DiskFile.GetData(EnumResult erParent) at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData() at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci) at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request) --- End of inner I tried to add all agent service users as sysadmin, didn't work. The funny thing is that the job, under the maintenance plan, appears on the TSX. When i create a standalone job and push it to the target, the job appears on the TSX(?!). Hope someone can help. Thank you in advance.

I am trying to Configure the Master target server / Multi server environment in Sql Server 2012. I changed : - MSXENCryptChannnelOptions-->Changed from 2 to 0 - AllowDownloadedJobsToMatchProxyName - changed from 0 to 1 on the target When I run the wizard I am getting below error >MSX Enlist failed for Job Server 'MasterServerName' > >The enlist operation Failed(Reason:SQL Server Agent Error: Unable to connect to MSX 'MasterServerName'(Microsoft Sql Server, Error : 22026) They both servers SQL Agents are running on the same windows service account. Any Suggestions on how to fix this? **Adding the Log:** Enlist TSX Progress - Create MSXOperator (Success) Checking for an existing MSXOperator. Updating existing MSXOperator. Successfully updated MSXOperator. - Make sure the Agent service for 'Test3' is running (Success) The service 'SQLSERVERAGENT' is running. - Ensure the agent startup account for 'Test4' has rights to login as a target server (Success) Checking to see if the startup account for 'Test4' already exists. Login exists on server. Checking to see if login has rights to msdb. Login has rights to msdb. Checking to see if user is a member of the TargetServersRole. User is a member of the TargetServersRole. - Enlist 'Test4' into 'Test3' (Error) Enlisting target server 'Test4' with master server 'Test3'. Using new enlistment method. Messages MSX enlist failed for JobServer 'Test4'. (Microsoft.SqlServer.Smo) ------------------------------ ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ The enlist operation failed (reason: SQLServerAgent Error: Unable to connect to MSX 'TEST3'.) (Microsoft SQL Server, Error: 22026)

I have a multi server administration environment and several maintenance plans deployed already. My MSX server is SQL2014. The problem i'm having is deploying maintenance plans to a 2008R2 named instance which is running alongside a default 2014 instance (which is working with MSX MPs already). I'm getting this error: Failed to import Maintenance Plan 'MSA backup' from MSX: Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored. ---> System.Runtime.InteropServices.COMException (0xC0011008): Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored. I added the account under which the agent service is running on the MSX to the sysadmin role on the named instance. I know it's trying to import to SSIS but there can only be one SSIS instance on a machine and that is the default, 2014 instance. Locally created MPs run without problems. I can provide more info if needed. I have googled without luck so far, but will continue. TY.

I've used Ola's scripts for quite a while at several companies, and just started a new job at a company who has already implemented MultiServer Agent Jobs to execute backups, DBCC CheckDB and IndexOptimization. For whatever reason, the person who implemented the solution in mulitserver jobs removed the output file "string" (i.e. the path to the Log folder on the instance). When I copied that value from Ola's scripts after I deployed them on my local machine, it caused 2 of the full backup jobs to fail because it "couldn't find" the path. The machine that the failures occurred on has 2 instances, and so far as I know, the path to "Errorlog" is default and based on the installation selection of that default. Both instances are SQL Server 2008 R2 Standard, while all the rest of our instances are 2014 Enterprise (which really should make no difference...but who knows?). I have removed the output file on the backup jobs so they will run successfully, but I'd really like to figure out the best way to implement this on all of our instances. At the very least, I suppose I could remove the 2 instances that are barfing with the path and recreate them on the local instances...but that really kills the benefit of using MultiServer SQL Agent jobs. Anyone have any ideas?

Is there a way to insert result of a query executed in Registered Servers into a view / sp / table? Currently I have locally setup a Registered Server on multiple servers to query the master database for each. I basically want to insert the result in a single container then read it by a job. It this possible?

I'm trying to set up multiserver administration on SQL Server 2016. I have two servers, one master and one target. I created a test job that does a simple select statement and then sends an email. I want that job to run on both master and target servers but it seems that I can't. I can't believe that's not possible (tried to google for that but didn't find anything).