What makes it strange is that you imagine with 6000 SQL servers, they would be used to doing that kind of stuff.
-----Original Message----- From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Friday, May 09, 2008 11:31 AM To: NT System Admin Issues Subject: RE: Rolling out MS SQL Stored Procedures Do you have IP connectivity? If so, it's pretty easy. What's it worth to you? :-) Seriously, put it in a file.sql text file and ship it out with oSQL.exe. No biggie at all. I've never done this with 6,000 (!!) SQL servers, but I've done it with several dozen. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Bryan Garmon [mailto:[EMAIL PROTECTED] Sent: Friday, May 09, 2008 2:23 PM To: NT System Admin Issues Subject: Rolling out MS SQL Stored Procedures I thought at one point Sunbelt sponsored a SQL group - but it's not listed here: http://www.sunbelt-software.com/Communities/ So if anyone knows what happened to it, or can point me to a better place to post this question I would appreciate it: A customer came to me with the following problem: There are over 6000 SQL Servers in their environment running MS SQL Server 2000 or MS SQL Server 2005. They have a stored procedure that needs to be added to each server. Aside from manually connecting to each one, has anyone had any experience automating this? ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
