|
|
Posted by Greg D. Moore \(Strider\) on 03/26/07 00:32
"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns98FF17565805Yazorman@127.0.0.1...
> As for the original question, I don't really have any good suggestion.
> It's not surprising that Mgmt Studio feels compelled to visit the
> database.
> Probably the best is to avoind Management Plans altogether, but just set
> up an SQL job that performs what you want to be done. Possibly you could
> create a Maintenance plan for a small number of databases, and then
> work with the plan in Business Intelligence Development Studio. (It is
> ab SSIS package as I understand it.)
And honestly I'd probably question why anyone has 6300+ databases on a
single server.
And would go further to suggest if you're really doing that, you're probably
better off writing your own tools to administer it.
It's really an edge case....
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
--
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com
Navigation:
[Reply to this message]
|