Database Mirror + Snapshot + Replication Questions

All,

We have SQL 2005 db mirror configured with a witness server for high availability. Node 1 is the principal and Node 2 is the mirror. A nightly job creates a snapshot on Node 2. The snapshot is used for previous day reporting queries. We have now been asked to present another copy of the database for near-time reporting. I thought about possibly adding a peer-to-peer replication as part of my environment but was hoping to see what everyone else out there is doing.

Regards,

Ian

I tend to use transactional replication with a pollinginterval of 1 and replicate the execution of stored procedures as much as possible.

Database marked as suspect when bringing up a clustered server

We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on the
database it tells me that nothing was changed because the flags are fine. I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort of
explanation of this behavior.
What does the SQL Server error logs say when the system is coming online and the databases are marked suspect?
I'd check the SQL Server cluster resource dependencies. When you say that after you've repaired everything and recycle SQL Server, how are you doing that? Are you just restarting services, taking cluster resources offline, taking the entire resource group offline, or using SQL EM to stop and restart the services?
Sincerely,
Anthony Thomas

"tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293D-46F4-9F5E-CAAB0A669B33@.microsoft.com...
We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on the
database it tells me that nothing was changed because the flags are fine. I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort of
explanation of this behavior.|||The SQL Server error log shows: Error 9004, Severity: 21, State 10
An error occurred when processing the log for database .....
As far as stopping and restarting SQL Server, I'm doing it from the Cluster
Administrator, go to the Active Resources folder and take SQL Server offline
and
then bring it back online. And then the database(s) will be available.
"AnthonyThomas" wrote:

> What does the SQL Server error logs say when the system is coming online and the databases are marked suspect?
> I'd check the SQL Server cluster resource dependencies. When you say that after you've repaired everything and recycle SQL Server, how are you doing that? Are you just restarting services, taking cluster resources offline, taking the entire resource g
roup offline, or using SQL EM to stop and restart the services?
> Sincerely,
>
> Anthony Thomas
>
> --
> "tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293D-46F4-9F5E-CAAB0A669B33@.microsoft.com...
> We have a 2 node clustered server (active/passive failover) that when it
> fails over (forced or otherwise) or if we just reboot the server, when it
> comes up, some of the user databases come up marked as suspect. Which
> databases get marked varies each time. If I execute an sp_resetstatus on the
> database it tells me that nothing was changed because the flags are fine. I
> then run a restore database with recovery it tells me that it completed
> successfully and processed 0 pages in 0 sec.
> I then go into the cluster administrator, take sql server offline and then
> bring it back up and the databases will be ok. We're looking for some sort of
> explanation of this behavior

Database marked as suspect when bringing up a clustered server

We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on the
database it tells me that nothing was changed because the flags are fine. I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort of
explanation of this behavior.The SQL Server error log shows: Error 9004, Severity: 21, State 10
An error occurred when processing the log for database .....
As far as stopping and restarting SQL Server, I'm doing it from the Cluster
Administrator, go to the Active Resources folder and take SQL Server offline
and
then bring it back online. And then the database(s) will be available.
"AnthonyThomas" wrote:
> What does the SQL Server error logs say when the system is coming online and the databases are marked suspect?
> I'd check the SQL Server cluster resource dependencies. When you say that after you've repaired everything and recycle SQL Server, how are you doing that? Are you just restarting services, taking cluster resources offline, taking the entire resource group offline, or using SQL EM to stop and restart the services?
> Sincerely,
>
> Anthony Thomas
>
> --
> "tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293D-46F4-9F5E-CAAB0A669B33@.microsoft.com...
> We have a 2 node clustered server (active/passive failover) that when it
> fails over (forced or otherwise) or if we just reboot the server, when it
> comes up, some of the user databases come up marked as suspect. Which
> databases get marked varies each time. If I execute an sp_resetstatus on the
> database it tells me that nothing was changed because the flags are fine. I
> then run a restore database with recovery it tells me that it completed
> successfully and processed 0 pages in 0 sec.
> I then go into the cluster administrator, take sql server offline and then
> bring it back up and the databases will be ok. We're looking for some sort of
> explanation of this behavior

Database marked as suspect when bringing up a clustered server

We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on the
database it tells me that nothing was changed because the flags are fine. I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort o
f
explanation of this behavior.What does the SQL Server error logs say when the system is coming online and
the databases are marked suspect?
I'd check the SQL Server cluster resource dependencies. When you say that a
fter you've repaired everything and recycle SQL Server, how are you doing th
at? Are you just restarting services, taking cluster resources offline, tak
ing the entire resource group offline, or using SQL EM to stop and restart t
he services?
Sincerely,
Anthony Thomas
--
"tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293D-
46F4-9F5E-CAAB0A669B33@.microsoft.com...
We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on t
he
database it tells me that nothing was changed because the flags are fine.
I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort
of
explanation of this behavior.|||The SQL Server error log shows: Error 9004, Severity: 21, State 10
An error occurred when processing the log for database .....
As far as stopping and restarting SQL Server, I'm doing it from the Cluster
Administrator, go to the Active Resources folder and take SQL Server offline
and
then bring it back online. And then the database(s) will be available.
"AnthonyThomas" wrote:

> What does the SQL Server error logs say when the system is coming online a
nd the databases are marked suspect?
> I'd check the SQL Server cluster resource dependencies. When you say that after y
ou've repaired everything and recycle SQL Server, how are you doing that? Are you j
ust restarting services, taking cluster resources offline, taking the entire resourc
e g
roup offline, or using SQL EM to stop and restart the services?
> Sincerely,
>
> Anthony Thomas
>
> --
> "tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293
D-46F4-9F5E-CAAB0A669B33@.microsoft.com...
> We have a 2 node clustered server (active/passive failover) that when it
> fails over (forced or otherwise) or if we just reboot the server, when i
t
> comes up, some of the user databases come up marked as suspect. Which
> databases get marked varies each time. If I execute an sp_resetstatus on
the
> database it tells me that nothing was changed because the flags are fine
. I
> then run a restore database with recovery it tells me that it completed
> successfully and processed 0 pages in 0 sec.
> I then go into the cluster administrator, take sql server offline and th
en
> bring it back up and the databases will be ok. We're looking for some so
rt of
> explanation of this behavior

Database mail running on cluster error

Hi

we are running Sql 2005 enterprise edition sp1 on a 2 node cluster.When we send a test message via database mail we recieve the following error

Date 3/7/2007 9:11:18 AM
Log Database Mail (Database Mail Log)

Log ID 5
Process ID 2892
Last Modified 3/7/2007 9:11:18 AM
Last Modified By JDG\pssqlservice

Message
1) Exception Information
===================
Exception Type: System.NullReferenceException
Message: Object reference not set to an instance of an object.
Data: System.Collections.ListDictionaryInternal
TargetSite: Microsoft.SqlServer.Management.SqlIMail.Server.Objects.Account GetAccount(Int32)
HelpLink: NULL
Source: DatabaseMailEngine

StackTrace Information
===================
at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.GetAccount(Int32 accountID)
at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.SessionManager.GetAccount(Int32 accountID)
at Microsoft.SqlServer.Management.SqlIMail.Server.Controller.CommandFactory.CreateSendMailCommand(DBSession dbSession)
at Microsoft.SqlServer.Management.SqlIMail.Server.Controller.CommandFactory.CreateCommand(DBSession dbSession)
at Microsoft.SqlServer.Management.SqlIMail.Server.Controller.CommandRunner.Run(DBSession db)
at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.ThreadCallBack.MailOperation(Object o)

Does anybody know what could be the problem here?

Just a guess here: No known FROM address provided...|||we do have a reply address configured in the batabase mail configuration.so it is not this