Database Mirror in a SQL cluster

I read that you can implement DB mirror in a cluster. However, someone else
said that you cannot. Does anyone have any ideas which is correct?
I found this
Database Mirroring and Clustering
The most important contrast between database mirroring and failover
clustering is the level at which each provides its redundancy. Database
mirroring provides protection at the database level, whereas clustering
provides protection at the server instance level. Another important
difference is that in database mirroring, the principal and mirror servers
are separate SQL Server instances with distinct names, whereas a SQL Server
instance on a cluster gets one virtual server name and IP address that
remains the same no matter what node of the cluster is hosting the instance.
If you need database protection at the server level (for example, your
application requires access to many databases on the same database server
simultaneously), failover clustering may be a more appropriate choice.
However, if you are concerned to provide availability for one database at a
time, database mirroring has a number of advantages.
Unlike clustering, database mirroring does not require proprietary hardware
and does not have a potential failure point with shared storage. Database
mirroring brings the standby database into service much faster than any other
high availability technology, and works well with new capabilities in ADO.NET
and SQL Native Access Client for client-side failover.
You cannot use database mirroring within a cluster, but you may consider
using database mirroring as a method for creating a hot standby for a cluster
instance database. If you do, be forewarned that because a cluster failover
is longer than the timeout value on database mirroring, a High Availability
mode mirroring session will react to a cluster failover as a failure of the
principal server. It would then put the cluster node into a mirroring state.
So the above answers my question. Since we have implemented SQL cluster
already, there is really no need to implement DB mirroring. Also since we
cannot have DB mirroring in a cluster.
"SAM" wrote:

> I read that you can implement DB mirror in a cluster. However, someone else
> said that you cannot. Does anyone have any ideas which is correct?
|||I think what they mean is that you can not use database mirroring in
place of shared storage when creating a MSCS SQL Cluster. You can
however set up database mirroring as an additional level of protection
to mirror from your SQL cluster to another SQL server outside of the
cluster for a extra level of redundancy - possible as a DR solution.
David A. Bermingham, MCSE, MCSA:Messaging
Senior Systems Engineer
www.steeleye.com
SAM wrote:[vbcol=seagreen]
> I found this
> Database Mirroring and Clustering
> The most important contrast between database mirroring and failover
> clustering is the level at which each provides its redundancy. Database
> mirroring provides protection at the database level, whereas clustering
> provides protection at the server instance level. Another important
> difference is that in database mirroring, the principal and mirror servers
> are separate SQL Server instances with distinct names, whereas a SQL Server
> instance on a cluster gets one virtual server name and IP address that
> remains the same no matter what node of the cluster is hosting the instance.
> If you need database protection at the server level (for example, your
> application requires access to many databases on the same database server
> simultaneously), failover clustering may be a more appropriate choice.
> However, if you are concerned to provide availability for one database at a
> time, database mirroring has a number of advantages.
> Unlike clustering, database mirroring does not require proprietary hardware
> and does not have a potential failure point with shared storage. Database
> mirroring brings the standby database into service much faster than any other
> high availability technology, and works well with new capabilities in ADO.NET
> and SQL Native Access Client for client-side failover.
> You cannot use database mirroring within a cluster, but you may consider
> using database mirroring as a method for creating a hot standby for a cluster
> instance database. If you do, be forewarned that because a cluster failover
> is longer than the timeout value on database mirroring, a High Availability
> mode mirroring session will react to a cluster failover as a failure of the
> principal server. It would then put the cluster node into a mirroring state.
> So the above answers my question. Since we have implemented SQL cluster
> already, there is really no need to implement DB mirroring. Also since we
> cannot have DB mirroring in a cluster.
> "SAM" wrote:

Database Mail

I'm keen to use database Mail in SQL 2005. It seems to work well and save's me having to implement a queue, audit logging for sent/errored etc, as SQL2005 can take care of all of that for me.

heres the but..

Is there any way to specify the "From" email address in sp_send_dbmail I know you specify it as part of email account & profile but I want to override that.

I just wanted to be able to keep an audit of all the emails that where sent from an asp.net website and thought i could get that functionality "out of the box" with SQL 2005 and DB Mail, but with out being able to set the from: address its not going to work

Any one have a sugesstion?

Thanks

If you really need this functionality, you can create a profile named aspnet and you can attach one account to this. but doing this you will not have the failover functinality of Databasemail. but you will have all the other features of database mail