Amy Russell (5/15/2009)

---

We're running SQL Server 2005 Standard x64 on a dedicated Windows 2003 x64 box. It has quad 6-core cpus and 48gb of RAM.

We have Max Memory set...

Check MSlogreader_history on distribution database

kiran_thota_kumar (5/14/2009)

---

Surely, this is not a H/W issue...

I am using a republisher scenario. From Publisher to republisher the data is moving with in no time. But it never reached from...

Sorry for the delay... been busy. 😉

I guess you do have to run the snapshot but I am not 100% sure where you are on this.

Suresh B. (5/15/2009)

---

Thanks for responding.

I meant number of latencies. Not the time gap.

Many publications cross the 3 minutes threshold that we have set.

They cross the threshold many times in a...

create table #LAYOUT

(

id int identity CONSTRAINT PK_layout primary key clustered,

start int,

[length] int

)

insert into #LAYOUT (start, [length]) values(1,...

"SQL profiler trace" gets my vote!

Marios Philippopoulos (5/13/2009)

---

TheSQLGuru (10/24/2008)

---

Can you please tell us which bug it was in CU9 that was causing the problem? I checked and cannot find any FIX from that update...

I think that Access is your bigger hit. If you can restrict how this is done through a predefined set of stored procedures you may be Ok.

If you need to...

Batching data is actually in your favor. How it is done is tricky in terms of how you index such table though.

You should look into minimizing page splits and ensure,...

If it is possible to do it all in one stored procedure it will be better for BOTH reasons, performance AND maintainability.

brade11 (5/13/2009)

---

Thanks for the info.

I have replication setup now on 3 different servers. (Pub, Dist, Sub)

I'm trying to replicate around 100 tables from a production server to a reporting...

In that link:

... If the account that is running SQL Server Agent does not have write access to the COM folder ...

Also the account used by the SQL Agent is...

george's question is "key". What are you going to do on the "replicated" database ?

I could suggest mirroring or log shipping but they may not do what you want.

RML51 (5/12/2009)

---

We have SQL 2005 SP3 with CU1 and this still hasn't been fixed. I looked through the CU3 release articles (which were published in April) and doesn't look like...