When doing an integrity Check, I choose All databases. However, it ends up
erroring out because one of the databases is offline. I would think that
since it's offline, it would not try to do an integrity check, but it does.
Am I missing something? or is this expected behavior? Do I need to just
choose specific databases? I'd rather not because databases get deleted and
added all the time.

Thanks

I don't know if there is a workaround other than explictily identify each
database. If you have a large number of databases, or are adding and dropping
databases from time to time, identifying databases explicitly is a
maintenance head. I found maintenance plans are just not customizable enough,
and have always opted for our own maintenance scripts instead.

Linchi

"Steven" wrote:

> When doing an integrity Check, I choose All databases. However, it ends up
> erroring out because one of the databases is offline. I would think that
> since it's offline, it would not try to do an integrity check, but it does.
> Am I missing something? or is this expected behavior? Do I need to just
> choose specific databases? I'd rather not because databases get deleted and
> added all the time.
>
> Thanks
>
>
>

I have a set of maintenance stored procedures that you could use if you like.
They ignore databases that aren't online.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com



"Steven" wrote:

> When doing an integrity Check, I choose All databases. However, it ends up
> erroring out because one of the databases is offline. I would think that
> since it's offline, it would not try to do an integrity check, but it does.
> Am I missing something? or is this expected behavior? Do I need to just
> choose specific databases? I'd rather not because databases get deleted and
> added all the time.
>
> Thanks
>
>
>