tailieunhanh - Microsoft SQL Server 2008 R2 Unleashed- P67

Microsoft SQL Server 2008 R2 Unleashed- P67:SQL Server 2005 provided a number of significant new features and enhancements over what was available in SQL Server 2000. This is not too surprising considering there was a five-year gap between these major SQL Server 2008 is not as much of a quantum leap forward from SQL Server 2005 | 604 CHAPTER 19 Replication It yields this result 1 PUBLISH AdventureWorks2O08 - Transactional 0 1 1 0 1 Address Person . Address Address 2 AddressType Person . AddressType AddressType 3 AWBuildVersion dbo . AWBuildVersion AWBuildVersion 4 BillOfMaterials Production . BillOfMaterials BillOfMaterials 5 Contact Person . Contact Contact 6 ContactCreditCard Sales . ContactCreditCard ContactCreditCard 7 ContactType Person . ContactType ContactType In addition sp_replcounters shows the activity of this replication session. You can see the volume of traffic and the throughput here exec sp_replcounters go It yields this result database repl_trans rate trans sec latency sec etc. AdventureWorks2008 0 For actual row count validation you can use sp_publication_validation which goes through and checks the row counts of the publication and subscribers exec sp_publication_validation publication PUBLISH AdventureWorks2008 - Transactional go It yields this result Generated expected rowcount value of 19614 for Address. Generated expected rowcount value of 6 for AddressType. Generated expected rowcount value of 1 for AWBuildVersion. Generated expected rowcount value of 2679 for BillOfMaterials. Generated expected rowcount value of 19972 for Contact. Generated expected rowcount value of 19118 for ContactCreditCard. Generated expected rowcount value of 20 for ContactType. Generated expected rowcount value of 238 for CountryRegion. Generated expected rowcount value of 109 for CountryRegionCurrency. Generated expected rowcount value of 19118 for CreditCard. Generated expected rowcount value of 8 for Culture. Download from Monitoring Replication 605 Another way to monitor replication is to look at the actual data being replicated. To do this you first run the SELECT count FROM tblname statement against the table where data is being replicated. Then you verify directly whether the most current data available is in the database. If you make a change to the data