User
Sent: Wednesday, November 12, 2008 7:05:01 AM
Subject: RE: SQL 2005 Database Mirroring Support
Hello.
When I turn on internal debugging
I get nothing at all.
This is a web application (using
Windows authentication) and the user has write permissions to the folder I
created where I wanted
anted to the user
running the application).
I am running SP1 on SQL Server 2005.
Any thoughts?
Cheers
Colin
From: Dag Christensen [mailto:[EMAIL PROTECTED]
Sent: 12 November 2008 07:46
To: Log4NET User
Subject: RE: SQL 2005 Database Mirroring Support
Importance: Low
You're using .NET f
.
Any thoughts?
Colin
From: Ron Grabowski [mailto:[EMAIL PROTECTED]
Sent: 11 November 2008 22:12
To: Log4NET User
Subject: Re: SQL 2005 Database Mirroring Support
Importance: Low
What does log4net report as the error when you
unning Sql Server 2005 SP1 or later? SQL server
2005 pre-SP1 doesn't officially support mirroring in production use.
Best wishes,
Dag
From: Ron Grabowski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 11:12 PM
To: Log4NET User
Subject: Re: SQL 2005 Database Mirrorin
What does log4net report as the error when you turn on internal debugging?
From: "Gourlay, Colin" <[EMAIL PROTECTED]>
To: Log4NET User
Sent: Tuesday, November 11, 2008 11:07:33 AM
Subject: RE: SQL 2005 Database Mirroring Support
Hi Dag.
: 06 November 2008 13:06
To: Log4NET User
Subject: RE: SQL 2005 Database Mirroring Support
Importance: Low
Should be handled transparently if you're using SqlClient or native client and
a correct connection string. I think log4net uses OLE DB by default, you might
want t
12:59 PM
To: Log4NET User
Subject: SQL 2005 Database Mirroring Support
Does log4net support the database mirroring feature in SQL 2005?
It logs quite happily when logging to our primary database but when I
failover logging ceases to work - in that nothing is logged - when I
failback log
Does log4net support the database mirroring feature in SQL 2005?
It logs quite happily when logging to our primary database but when I failover
logging ceases to work - in that nothing is logged - when I failback logging
works as before. The mirroring has been configured correctly (test has bee
