RE: Database Mirroring or Log Shipping?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello Josh,

If you would like to set up Log Shipping and afraid of ONLY deprecated in
future versions than you can do it manually too.

Log Shipping nothing but moving tlog from Primary to Secondary once restored
the Full backup on Secondary.

Following might help you to do manual setup.

http://www.nyx.net/~bwunder/sql/logSync.htm

Good Luck!!!


"hfdev" wrote:

I made a mistake when I quoted the technet article. Here is the statement
that says the mirrored db can't be accessed directly:

"Because the mirror database is in a recovering state, it cannot be accessed
directly. You can create database snapshots on the mirror to indirectly read
the mirror database at a point in time."

Again, snapshots are not an option for us b/c we have SQL 2005 STD.

We also can't use a new copy of SQL 2005 Enterprise edition as the mirror
server and take snapshots because as I understand it, you have to keep the
versions/editions all the same for compatibilities sake.

Maybe Log Shipping is an alternative, but thought that I read that Log
Shipping be deprecated in future versions.

Again, advice is greatly appreciated,

--
Josh Blair (hfdev)
HydraForce, Inc.


"hfdev" wrote:

Hello,

I am researching database mirroring and log shipping to determine if either
will help my organization achieve a certain goal.

We are looking for a way to make our production ERP database (currently ~30
GB in size) available in near real-time on another server for read-only
access from numerous client applications and SSRS.

We have SQL Server 2005 STD so snapshots are out of the question.

Replication is not an option: not supported by ERP vendor, they say the db
isn't structured in a way that will support replication.

I was thinking database mirroring would be perfect until I read similar
statements to thie following in a number of older publications:

"The mirror database must be initialized from a restore of the principal
database with NORECOVERY, followed by restores in sequence of principal
transaction log backups."

and

"The mirror database must have the same name as the principal database."

Database Mirroring in SQL Server 2005 (published on April 1, 2005)
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx

Q: With Database Mirroring on SQL 2005, can you access the data on the
mirrored copy (secondary) to use as a read-only datasource for client apps
and SSRS?

Can you recommend any other alternatives?

Thanks in advance,

--
Josh Blair (hfdev)
HydraForce, Inc.
.

Relevant Pages

  • RE: Database Mirroring or Log Shipping?
    ... I used SSMS to configure the Log Shipping in 2005 and it seems to get the ... Josh Blair (hfdev) ... "Because the mirror database is in a recovering state, ...
    (microsoft.public.sqlserver.replication)
  • Re: Is SQL2005 Database Mirroring ready?
    ... I had to fail the mirror ... If I do fail over to my log shipping machine (by ... > some basic requirements - it is in fact the same database and the ... > transaction log backup contains the next LSN in the sequence. ...
    (microsoft.public.sqlserver.replication)
  • Log Shipping fails on some database AFTER 10th or 11th iteration.
    ... deploying Log Shipping on our SQL server. ... 'Log Ship' under this configuration, with different copy & load schedules. ... The initial configuration, creation of the destination database, restoration ...
    (microsoft.public.sqlserver.replication)
  • log shipping one database two times to the same SQL instance
    ... I m sorry for not being able to help you out under sql 2005, instead i request your help in implementing the same scenario in SQL 2000. ... I have a problem log shipping one primary database to two databases when the ... can not use different copy and restore schedules for the second log ship. ...
    (microsoft.public.sqlserver.server)
  • Re: Is SQL2005 Database Mirroring ready?
    ... performed before you try to initiate the failover to the log shipping ... > over, then setup log shipping on the mirror, but not define the ... >> some basic requirements - it is in fact the same database and the ... >> transaction log backup contains the next LSN in the sequence. ...
    (microsoft.public.sqlserver.replication)