DB Maintenance Plan SQL 2005 on 6300+ Database

Hi,
We have a SQL-cluster with over 6300 databases, most of them pretty
small in size and usage.
For this reason all these databases are on auto-close ( Otherwise SQL
would need many many gigabytes ).
We've recently upgraded to SQL 2005 because of the Management Studio,
because the EM is unusable on a SQL-Server with lots of databases.
But whenever you choose 'all user databases' or 'all databases' in any
of the DB Maintenance task, MSSQL begins starting up every database
which takes about 30 minutes. Until then, you cannot use your Studio
anymore.
My question : is there a possibility to avoid this behavior, it should
not go and check all those db's, just add my task.
PS : Detaching these databases is not an option ...
Thanks in advance,
Sven Peeters
"Icemokka" <icemokka@.gmail.com> wrote in message
news:1174750670.801708.131440@.e1g2000hsg.googlegro ups.com...
> Hi,
> We have a SQL-cluster with over 6300 databases, most of them pretty
> small in size and usage.
> For this reason all these databases are on auto-close ( Otherwise SQL
> would need many many gigabytes ).
> We've recently upgraded to SQL 2005 because of the Management Studio,
> because the EM is unusable on a SQL-Server with lots of databases.
> But whenever you choose 'all user databases' or 'all databases' in any
> of the DB Maintenance task, MSSQL begins starting up every database
> which takes about 30 minutes. Until then, you cannot use your Studio
> anymore.
> My question : is there a possibility to avoid this behavior, it should
> not go and check all those db's, just add my task.
> PS : Detaching these databases is not an option ...
>
I would not expect all the tools to work very well with that many of
auto-close databases. I would use SSIS to create the maintenance plan for a
single database, and then use a foreach loop to apply that to each database.
Or perhaps even script it with SMO.
David