First, what kind of replication are you using ?

Second what do you mean by "replication fails" ?

When the tables are large these type of columns increase overhead in "write" performance.

Although this is a SQL 2000 issue and you are in a 2005 forum I am going to give you a clue on how to solve it.

Don't disable the trigger...

But do you want the changes at subscriber to affect the publisher, right?

Also if you have tables without PK, fix them!

I have servers with similar setup. Distributor on the subscriber only makes things worse because usually subscribers will also have intensive reads. To achieve performance at that level you will...

Transactional replication does NOT requires a GUID column. Merge does.

It will work but the root cause should be investigated. It usually leads to inefficient queries and unnecessary large DML activities.

ichbinraj (5/5/2009)

---

Hi ,

I am planning to do on-line Reindex for 100 tables one by one.

Is it possible to put them in script like when 1 st table done...

You may want to take a look at SQL Packager

Also depending on fragmentation levels you could chose to DEFRAG instead of REBUILD.

Incidentally, DEFRAG is always online and it is available on Standard Edition as well.

At my job we try to minimize reliance in SQL Server Agent and SSMS UI. So we run our own replication checks. Latency is readily available from distribution DB and...

There is an entry in Connect saying that it was fixed in 2008. People with 2005 SP2 are complaining.

Your build number matches SP3 but I don't think they did...

I believe this is still a problem in 2005.

How did you specified the new value, though Replication Monitor or on the Alert itself?

Note that there are cases in which the subscriber could be used as a DR DB.

In that scenario, you can setup a trigger on the tables created by replication...