![]() And we could choose to not have the results merged. We could remove the server name if required, although that doesn't seem very useful. We could add a column that shows our login name for each server to the results. In Tools, Options, Query Results, SQL Server, Multi-server Results, we have these options: We can configure several things about how this happens. It has just presented the results to us as though they are a single set of results. ![]() Under the covers, it has run the query individually against each server. If I type the query SELECT and click Execute, I see this:Įven though this looks like a single result set, this is just a SQL Server Management Studio (SSMS) trick. The window color at the bottom has changed from the default, and in the bottom right, we can see that the window is connected to the local server group: When you click this, it opens a query window for the group of servers. I'll talk about policies another day but notice that you can import or check (evaluate) policies across a whole group of servers.īut the option that interests me today is the New Query option. ![]() If I right-click the group, rather than any individual server, we get these options: The Development Servers group has three database servers in it. I've created three local server groups, for my development, UAT, and production servers. What I didn't really talk about though, is what you can do with these groups of servers, rather than just executing queries on an individual server. In an earlier post, I mentioned that you can create a registered list of servers, either in Local Server Groups or stored in a Central Management Server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |