﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Dinesh Asanka / Article Discussions / Article Discussions by Author  / Applying Your Scripts across Multiple SQL Server Databases / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sun, 19 May 2013 00:29:45 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Applying Your Scripts across Multiple SQL Server Databases</title><link>http://www.sqlservercentral.com/Forums/Topic472064-144-1.aspx</link><description>[b]I personally prefer QueryBlaster (www.QueryBlaster.com). I have been using it on my production servers for a few months now and I love it.  No more skipped over databases and I'm finished in a fraction of the time! :cool:[/b]</description><pubDate>Thu, 11 Sep 2008 01:08:49 GMT</pubDate><dc:creator>brad.buntin</dc:creator></item><item><title>RE: Applying Your Scripts across Multiple SQL Server Databases</title><link>http://www.sqlservercentral.com/Forums/Topic472064-144-1.aspx</link><description>I concur with Anirban.  We have to use it a lot more in production to identify any pitfalls.  However, I am using the product in my production environments and so far it does what it says on the tin.</description><pubDate>Thu, 20 Mar 2008 03:35:32 GMT</pubDate><dc:creator>back_of_the_fleet</dc:creator></item><item><title>RE: Applying Your Scripts across Multiple SQL Server Databases</title><link>http://www.sqlservercentral.com/Forums/Topic472064-144-1.aspx</link><description>The tool seems cool. But I should not comment on these in positive or negative unless and until using it. As the tool is new we will know the advantages and disadvantages of it when it will be extensively used in production.Thanks to the author for explaining it well. :)Regards</description><pubDate>Thu, 20 Mar 2008 03:29:28 GMT</pubDate><dc:creator>Anipaul</dc:creator></item><item><title>RE: Applying Your Scripts across Multiple SQL Server Databases</title><link>http://www.sqlservercentral.com/Forums/Topic472064-144-1.aspx</link><description>I am responsible for 16 databases on a single server - each database is the same 'shape' (ie. tables/views/stored procedures) etc., but contains data from disparate sources.  When applying database changes I had a tick list to make sure the same changes were applied to each database, and in some cases there were multiple scripts to be applied.  I'd sit in front of Management Studio waiting for a script to complete (which, when data changes were being made, could take some time over millions of rows).  Then I'd move on to the next database.Then I bought Multi Script which now manages the whole lot for me.  I've binned my tick lists.</description><pubDate>Thu, 20 Mar 2008 03:11:59 GMT</pubDate><dc:creator>back_of_the_fleet</dc:creator></item><item><title>Applying Your Scripts across Multiple SQL Server Databases</title><link>http://www.sqlservercentral.com/Forums/Topic472064-144-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/Product+Reviews/62584/"&gt;Applying Your Scripts across Multiple SQL Server Databases&lt;/A&gt;[/B]</description><pubDate>Thu, 20 Mar 2008 00:01:45 GMT</pubDate><dc:creator>Dinesh Asanka</dc:creator></item></channel></rss>