Database mirroring scenario

We are looking to establish a mirror server with witness. We have some
databases that have interdependencies that concern me. If one of the db's
goes offline on the primary for any reason and only that db fails over to
the mirror then we have an issue when the other db's on the primary continue
operating and are not available on the mirror.
Is there some way to monitor the failure and force the other dependent db's
to go offline forcing them to failover as well?
We had a cpu go out on our primary server last week which caused some
hiccups while the bios was evaluating the issue. Now I'm tasked with
getting this environment tested quickly...
Any help is greatly appreciated!!!
Thanks.
You can use the dmv for this:
SELECT mirroring_state_desc FROM sys.database_mirroring WHERE database_id =
DB_ID ('MirroredDatabase');
GO
Then when your database fails over you can issue the following
alter database othermirroreddatabases set partner failover
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:euW%23ZPwTIHA.748@.TK2MSFTNGP04.phx.gbl...
> We are looking to establish a mirror server with witness. We have some
> databases that have interdependencies that concern me. If one of the db's
> goes offline on the primary for any reason and only that db fails over to
> the mirror then we have an issue when the other db's on the primary
> continue operating and are not available on the mirror.
> Is there some way to monitor the failure and force the other dependent
> db's to go offline forcing them to failover as well?
> We had a cpu go out on our primary server last week which caused some
> hiccups while the bios was evaluating the issue. Now I'm tasked with
> getting this environment tested quickly...
> Any help is greatly appreciated!!!
> Thanks.
>
sql