Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Replication / June 2006

Tip: Looking for answers? Try searching our database.

Replication Monitor reveals poor performance - but what to do to f

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
SteveM - 29 Jun 2006 04:14 GMT
The client production server CPU starts thrashing. Task manager indicates
that SQL server is gobbling CPU cycles. Having a look at the replication
monitor, it is obvious that indivual synchronisations to the mobile devices
are taking significantly longer expected.

Observing an indivual synchronisation attempt, the Upload changes to
Publisher rows are very quickly resolved.

The Download changes to Subscriber seems to take up a very long time.

Along the way, the estimated completion does a few interesting things, like
going from 100% complete with no estimated time to complete, back to
seomthing like 77% with 2 minutes left to complete.

This sort of behaviour occurs when there are only a hundred rows to download.

Synchronisations for minimal amounts of data suddenly taking anywhere from 2
to 15 minutes. Totally unacceptable form the client perspective but seems
that 2005 behaves quite different from 2000 and the tricks are yet to reveal
themselves.

Note - It is a server hardware issue as there is in excess of 3 GB ram, the
database is on a SAN and there are 4 3Ghz CPUS in operation.

Any possible help appreciated as this issue is beginning to drag on.
Paul Ibison - 29 Jun 2006 10:30 GMT
Steve,
I'd probably raise a PSS call for this. You could use profiler/dbcc
inputbuffer etc to try to determine what the issue is, but this sort of
debugging is routinely done by PSS and you might have uncovered a bug they
alreadty know about.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.