Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SQL2008 Transactional ReplicationSQL2008 Transactional Replication
Previous
 
Next
New Post
4/2/2010 12:36 PM
 

Anyone know if DNN will function with SQL2008 transactional replication enabled?  We are looking to setup a disaster recovery system that will essentially be a replica of our current production environment.  We are currently running DNN 5.1.4 (community edition).

 
New Post
4/2/2010 5:00 PM
 

Tony,

I don't see a reason why a DNN database would not work.  However, my experience is based on SQL 2000. 

From a disaster recovery point of view,  a typically DNN database has relativity few updates - However it does depend on the type of site (social sites being the obvious difference)  The type of database duplication really depends on the recovery time requirement of your DRP plan.

You may want to look at just performing frequent backups (every 4 hours?) .  Additionally you can be rolling your transaction logs often to get even closer to real time.  Transaction log shadowing is also something to consider.

Paul.

 
New Post
4/2/2010 5:27 PM
 

Replication is a viable option, in fact I have set up a few. As Paul alluded to, a more simple solution may be effective, such a trans-log shipping or simpler yet, just a cold stand-by where you can recover form a set of full and transaction log backups. The later has proven very effective for us and  a transaction log backup as often a 2 hours may be in order depending on site usage. These back-ups are often placed on a third server (behind the firewall) so either the primary or secondary DB has access to them in case they're needed.

One thing to consider is that upgrades often call for a database to have new objects added, dropped or changed, this can be a replication nightmare.

HTH



 
New Post
9/8/2011 4:13 PM
 
I have been struggling with DNN SQL replication to the extent that my eyes are crossed and my head is sore and bloody from beating it against the wall.

I get replication working, but invariably I get PK violations as a result of PK collision and the dnn application breaks.  The primary table is dbo.eventLog when I replicate.  What articles need to be published?  If you have any guidance here I'd love to hear from you!

-=jd
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SQL2008 Transactional ReplicationSQL2008 Transactional Replication


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out