Bertrand Rohrbock - All Comments

re: Installing multiple instances of SQL server without rebooting

Joy — Thu, 04 Feb 2010 10:01:54 GMT

Great! The articles so far have been full of great material. Glad to hear the serious will continue. Keep 'em coming!

re: Restoring MSDB across instances, a bad idea

AdolphH — Mon, 07 Dec 2009 03:42:18 GMT

Restoring MSDB across instances is not necessarily a bad idea, as long as SQL is installed the same way on all servers. I’ve always had good luck with that. Unfortunately, that did not happen this time, and your script prevented us from having to reinstall.

Thanks.

re: Restoring MSDB across instances, a bad idea

Brian — Thu, 03 Dec 2009 17:49:56 GMT

Thanks! I appreciated the script! Helped me out a lot!

re: Restoring MSDB across instances, a bad idea

Amit — Wed, 28 Oct 2009 05:59:28 GMT

what a script mate.great...it wirks like magic...

re: Restoring MSDB across instances, a bad idea

Andrey — Fri, 15 May 2009 10:23:21 GMT

thanks a lot!

re: Restoring MSDB across instances, a bad idea

Paul — Tue, 21 Apr 2009 14:34:52 GMT

We've moved/renamed many servers over the last couple of years running SQL 2000. It has the same problem as well. In particular, any scheduled jobs for SQL Agent will still reference the old server name. Manual update of system table is required.

re: Restoring MSDB across instances, a bad idea

Josh — Tue, 10 Mar 2009 20:41:50 GMT

I moved MSDBs across instances as well...in hindsight it was a bit more trouble than it was worth. Your fix saved my butt. Thanks

re: Restoring MSDB across instances, a bad idea

Henning — Sat, 25 Oct 2008 20:28:34 GMT

Thanks !

re: Restoring MSDB across instances, a bad idea

DavidB — Sun, 10 Aug 2008 17:34:30 GMT

You are a genius. Thank you.

re: Restoring MSDB across instances, a bad idea

BertrandR — Thu, 19 Jun 2008 07:12:39 GMT

Maybe your setup has something I didn't account for in the script. Do a select on msdb.dbo.syssubsystems and look for the DLL files on your setup, then modify the path's to the DLLs. Good luck !

re: Restoring MSDB across instances, a bad idea

Ken — Tue, 17 Jun 2008 21:17:46 GMT

Hi,

I am getting this

Message

[125] Subsystem 'ActiveScripting' could not be loaded (reason: The specified module could not be found)

I used your script and executed. But when I restart the sql server the error logs are giving the same error.

re: Object references and SQL

Christian Hageraats — Mon, 26 May 2008 15:10:56 GMT

Dear Bertrand, It would be nice if you declare the @CmdStr variable. Plus if you are using a different schema then dbo you can place the schema name with the table name. Tables(".table1").Indexes("index1").Script(5)' With best regards, Christian Hageraats

re: Restoring MSDB across instances, a bad idea

Brandon M — Wed, 12 Mar 2008 19:10:33 GMT

Many thanks to you for not only the explanation of the problem, but for the script as well! I have been fighting these "stored path" problems for the last few days, but when this one happened, I found your page and my problem was solved immediately!

Thank you, thank you, thank you!

re: Restoring MSDB across instances, a bad idea

BertrandR — Mon, 14 Jan 2008 10:38:21 GMT

Ah that explains it, good luck !

re: Restoring MSDB across instances, a bad idea

Dmitry — Mon, 14 Jan 2008 10:34:37 GMT

It's a my mistake

Parameter "Allow service to interact with desktop" on SQL Agent was checked

:-) Thank you again for the script !