chileu17 (2/18/2009)

---

Thanks for the replies but is there any "official" link or site where I could find this??? The thing is that I have to support why it's a good...

833.33 trasactions/sec is respectable if sustained.

Replication can handle it if correctly configured so that distribution does not becomes a bottleneck

I have replicated Billion+ row tables without problem but it...

Make sure you set the DB to compatibility mode 9.0, Update stats with fullscan,all and update usage!

That should do it!

"SELECT INTO" locks metadata tables for the duration of the operation.

Trace flag 1807

Use it at your own risk!

500MB is not a lot for a 1TB database.

You should have an Idea how much time it takes on your hardware to do that.

Hopefully you are taking advantage...

Default Trace overhead is "minimal"!

with transactional replication by default the replicas are "read-only" if you modify the replica table you will receive primary key violation errors.

If you expect to change data on the replicated...

You need to ensure that on the "destination object owner" property of your table articles you specify the "right" schema.

By the way you have to re-create your replication settings.

ritesh (2/18/2009)

---

Hi All, While doing a transactional replication i got the following error in the log reader agent status:

"The process could not execute 'sp_repldone/sp_replcounters' on 'servername'.

and the synchronysation status gave...

TroyG (2/16/2009)

---

Well in the interests of completness in case someone else experiences this issue here is the resolution we had to do:

After getting confirmation from Microsoft it would appear as...

This message tends to happen at index creation time after the data has been transferred by the snapshot job

if you want to FORCE lock type on both use "WITH (ROWLOCK)"

In addition failover clustering does NOT recover client connections that could time-out.

Connection interruption code *must* be present on the client-side code!

matt.ma (2/11/2009)

---

Hi

I am implementing transaction replication using the 'sync with backup' option so that I can still have point-in-time recovery available while scaling out the application to a separate...