InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 18:22:15 GMT20http://www.sqlservercentral.com/Forums/Topic552398-1365-1.aspxWhat a great tip. Thank you! It infuriates me that Microsoft wouldn't document better something as useful as this.Thu, 21 Aug 2008 22:22:03 GMTmishalubahttp://www.sqlservercentral.com/Forums/Topic552398-1365-1.aspxThat was extremely useful, thank you.Wed, 20 Aug 2008 13:51:06 GMTtimothyawisemanhttp://www.sqlservercentral.com/Forums/Topic552398-1365-1.aspxyeah thats the problem, we here supporting 100+ environment, without access to the box, only sysadmin access...making a check everyday to ensure all of them are in sync and basic configuration is not changes...ddl changes, security changes tracking are some of the tasks needed to ensure a good control...as of now using sqlcmd to do this tasks...it was quite painful thoughlets hope somebody has explored that option and have right solution...Mon, 18 Aug 2008 17:30:10 GMTPrakash Hedahttp://www.sqlservercentral.com/Forums/Topic552398-1365-1.aspxThe multi server query is actually executed as separate batches on each server, so any statements being run are still batch scoped which means they will complete inside their respective connection. So if you issue a create the table statement, it is run on each server in the database that is selected in the dropdown. The same goes for Inserts. The aggregation of the data and display with server name happens client side by SSMS. This is why you can control the ServerName being ON/OFF with a change to the Options under Tools.Your question actually points out an extremely valuable use for this that I never actually considered previously. I have seen a number of questions where someone wants to update a database across multiple servers, like a development farm with the same piece of code. I worked in one company that had 24 different development instances to manage consistently. Changing one core procedure would require changing the connection 24 times to deploy it to everywhere. This is easily accomplished with Multi-server queries, and I'll have to call a buddy of mine who actually has a nightmarish development environment like I describe above and tell him about this.Mon, 18 Aug 2008 16:51:21 GMTJonathan Kehayiashttp://www.sqlservercentral.com/Forums/Topic552398-1365-1.aspxThanks, i was using this technique for a while, what i couldn't figure out it how the resultset of all these servers can be store in one table in one database for future usage?Appriciate any response...Thx ~ PrakashMon, 18 Aug 2008 15:19:25 GMTPrakash Hedahttp://www.sqlservercentral.com/Forums/Topic552398-1365-1.aspxExcellent observation, Jonathan. thanks for passing it along. :)Thu, 14 Aug 2008 12:23:53 GMTRBarryYounghttp://www.sqlservercentral.com/Forums/Topic552398-1365-1.aspxPretty cool Jonathan. Yet another reason to upgrade to 2008.Thu, 14 Aug 2008 07:02:05 GMTKenSimmonshttp://www.sqlservercentral.com/Forums/Topic552398-1365-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/SQL+Server+Management+Studio/63650/">Multiple Server Queries with SSMS 2008</A>[/B]Wed, 13 Aug 2008 21:26:57 GMTJonathan Kehayias