Viewing 15 posts - 256 through 270 (of 279 total)
Question #2, also taken from BOL:
Database mirroring partners and witnesses are supported by SQL Server 2005 Standard SP1 and later versions, and by SQL Server 2005 Enterprise Edition SP1 and...
February 16, 2009 at 9:55 am
For your question #1, taken from BOL:
To force service in a database mirroring session
1. Connect to the mirror server.
2. Issue the following statement:
ALTER DATABASE SET...
February 16, 2009 at 9:42 am
Great article Gail..... It's now permanently bookmarked 🙂
February 16, 2009 at 7:39 am
Transaction Log backups <> Mirroring. Those are 2 totally different things.
What you see on your Mirror server is the way it should be... it is in Restoring mode.
February 12, 2009 at 9:18 am
Did you just upgrade to SP2 ? I've seen this happening and re-applying the database engine part of the SP2 fixed this....
February 12, 2009 at 8:46 am
The "Restoring..." on the mirror is the default state. Remember when you set it up, you restored the database and left it in that state so the log transactions can...
February 12, 2009 at 8:38 am
... and that is exactly the reason why the mssqlsystemresource.* should be backed up manually after any upgrade..... Just as a reminder, this DB is in the same location as...
February 12, 2009 at 7:32 am
As mentioned above, it is the number of transactions that will be the issue. We mirror a 700++ GB database to a remote location and it usually is between 40...
February 12, 2009 at 7:28 am
Have you checked that the Operator is Enabled (in the Operator properties)?
Check the Database Mail log to see if anything is causing that error: Database mail -> View Database Mail...
February 11, 2009 at 11:19 am
Derek Dongray (2/9/2009)
Of course, if you want to be really silly you can docreate table # (_ int)go
insert # select 1
go
select * from #
I'll use that next time I need...
February 9, 2009 at 8:19 am
Jeff Moden (2/6/2009)
.... One of my major points was that someone posted some a link to some pretty bad T-SQL and the race between that
and a CLR and...
February 7, 2009 at 7:25 am
in our case, no... we still do backups as before, both full and transaction logs..... these get also backed up via our backup service.
Even with a mirrored database, you still...
February 5, 2009 at 2:03 pm
true.... both of our servers are pretty beefy..... even with a lot of transactions I haven't seen it lag behind more than a few seconds.
February 5, 2009 at 1:48 pm
We run High performance async mirroring and have no overhead at all that could be measured. The mirror DB's are synced up to the second (ie, basically no delays)
February 5, 2009 at 1:05 pm
Don, here is a VERY good example on why CLR's sometimes ARE the way to go:
SQL Server CLR function to improve performance of validating email addresses [/url]
February 5, 2009 at 8:51 am
Viewing 15 posts - 256 through 270 (of 279 total)