June 22, 2008 at 10:27 pm
thank you all for your kindest responses.
but our requirement has been slightly changed i.e.
when link between pune and mumbai goes down, pune users will updating localdb and mumbai users will be waiting for link to get online, all the transaction will always be done at pune office and mumbai users will be performing read only operation from mumbai server and write operation to pune server
2 servers i.e, pune(primary), mumbai(secondary)
all read write operations at pune server will be done by pune user
all read operation by mumbai users will be done from mumbai server
all write operation by mumbai user will be done at pune server
when the link between pune and mumbai goes down, pune user will be performing read write operation at pune server only, and now mumbai user can do nothing except reading from mumbai server
now with this situation which architecture would be most feasible.
thanks
Vinit
June 24, 2008 at 4:47 pm
Database mirroring will not work for you definitely. Mirror database will not available for reading.
You can use transactional replication or log shipping. Log shipping is easier to setup and troubleshoot. It would be my preference if latency is not an issue. Also, it doesn't require additional database (distributor in replication).
June 24, 2008 at 10:35 pm
Yep I would use logshipping probaly every 1hr depends on how fast your line is and the over head on these systems.
Regards,
Terry
June 25, 2008 at 7:07 am
Mirror database will not available for reading.
If you put a snapshot on a mirrored database, you can use the database for read operations
About logshipping: If you apply logs, no one can access the database during the log apply
Wilfred
The best things in life are the simple things
June 26, 2008 at 7:08 am
you have described a typical simple transactional replication scenario, so this sounds like your best bet.
log shipping will make the mumbai db unusable whilst the log so being loaded, so unless you don't mind mumbai users being kicked off when logs are restored this is out.
snapshot off of a mirrored databases could be done, it all depends on latency you require, If you want minimal latency then transactional replication is way to go.
If you are happy with mumbai data being say a day old then you have many options:
snaphot replication daily
snaphot of a mirrored database
log shipping but restore all logs once a day
restore a full database backup nightly
of those restore a full backup nightly is the simplest and the way I would go, setting the db to read_only in mumbai.
If using replication remember there are limitations such as having a primary key on all replicated tables.
---------------------------------------------------------------------
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply