nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DD or Replication

ProfessorX

1 website, 2 webservers, 2 database servers
Each webserver points to it's own database server.

For OD we are doing a fan out---> box 1 and box 2

But for DD I'm not sure if we should do the same, or use replication(SQL 2000). We are planning on doing replication but I let our DBA know it must be realtime replication in order for the publishing from TS is sync across both DB.

But I wonder if we should go fan out with DD (well that's what I call it). The only real reason I can come up with to do the fan-out of DD is because if something fails I will know right away, as oppsed to wondering if replication failed if the DB are not in sync.

Any thoughts or feed back would be great help? What are you doing?

Thanks in advance.

The Professor-

Find more posts tagged with

Comments

Migrateduser

DataDeploy will let you deploy to both databases, but they are executed serially. So you don't get the "synchronization" across the two databases. But at least if one of the deployments fails, you'll know that the databases are out of sync.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

You could use multiple database destinations or have a chained deployment by specifying multiple exec-deployments where each exec-deployment points to a DB deployment within a deployment section. This way even if one of the db fails to commit the whole DD transaction is rolled back.