Replication Snapshot,Distribution Agent Problem. | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Replication Snapshot,Distribution Agent Problem.

Hi Gurus, I have setup Transactional Replication between two servers.Publisher and Distributor on Server 1 and Subscriber on server 2. I took the Initial Snapshot of the Publishing Tables and sucessfully applied it to the
Subscriber. I stopped all the Agents. Next day I started all the Agents, Hoping to get an Incremental Push to the Subscriber.
But to my supprise I noticed that the Subscriber data has become Zero and the Initial
snapshot started reapplying again on the Subsciber database. And Snapshot Agent does not start again. Please help me to setup Incremental Data transfer and also
Tell me Why does the Snapshot Agent does not start again ? Also, The Performance monitor Peaks(Avg Disk Queue Length)are always high for the Subscriber.Please help me to understand How to keep Those Peaks Down. Urgent Please. Thanks -Rajesh.
raj

—""""Next day I started all the Agents"""", Hoping to get an Incremental Push to the Subscriber.
But to my supprise I noticed that the Subscriber data has become Zero and the Initial
snapshot started reapplying again on the Subsciber database.— When you run all the agents including snapshot it removed old data from subscriber database and reapply frest data from publisher database. Snapshot Agent runs once when you established replicaiton [choosing initialize subscriber database] The Snapshot Agent is used with all types of replication. It prepares schema and initial data files of published tables and stored procedures, stores the snapshot files, and inserts information about initial synchronization in the distribution database. The Snapshot Agent typically runs under SQL Server Agent at the Distributor and can be administered using SQL Server Enterprise Manager or the ActiveX® Snapshot Control. There is one Snapshot Agent per publication. —Also, The Performance monitor Peaks(Avg Disk Queue Length)are always high for the Subscriber.Please help me to understand How to keep Those Peaks Down.— Select data for replication which is relavent..instead replicating whole database. by the way what RAID level you are using at subscriber side and speed of disk…and how many transaction per second your publisher database replicate to subscriber…what is the latency you are facing.
Deepak Kumar –An eye for an eye and everyone shall be blind
Hi Ok, I fixed this problem.Now, the problem I am facing is I have Transaction Replication setup.
on my Publisher db I have run some scripts which effected the tables and the struture of tables
have changed. Now instead of applying all the tables chosen for replication I would like to apply
replication for a few tables of the Subscriber.
Can someone give hints on this. Can someone guide me to use right BOL. Very Urgent Please. Thanks,
raj
You will have to create snapshot of database once again..if you have already executed scripts on database that was being replicated.. now before taking snapshot alter article of publication database for table, that only you need now. Check ‘replication’ from indexes of BOL. http://www.sql-server-performance.com/transactional_replication.asp
http://www.awprofessional.com/articles/article.asp?p=170234&rl=1 Deepak Kumar –An eye for an eye and everyone shall be blind
]]>