Replication commands

How to identify how much replication commands are getting replicated from publisher to distribution database in a seconds?

Please tell me all methods to validate this parameter.

e.g. counters for perfmon if any or DMV's or by any other methods.

And recommended transaction per second (number of replication command in second)that can occur between publisher and distributor?
LVL 5
VIVEKANANDHAN_PERIASAMYAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jaLoudenCommented:
Hey VIVEKANANDHAN_PERIASAMY

It does depend somewhat on your Replication type, I'm guessing from your question you are using either transactional or merge.

The best place to start is here

http://technet.microsoft.com/en-us/library/ms152751.aspx

The replication monitor is the easiest way to monitor things as it presents a nice GUI. It does hide some of the details that you are after. I'm guessing the RMO's are what you will want to use as they provide the lower level of detail.

As to the number of transactions per second, like most things IT..it depends. Where I work we have 300+ sql servers, some of which are at the end of unstable network links.  Of those links that are stable network QOS prevents us from flooding the link. So we use merge replication because it can handle network loss, slow links. In your situation if you are replicating between two datacentres and you have massive low latency links you might want to use transactional replication. In this situation it depends on the resources allocated to your sql servers, eg disk, cpu memory, network etc etc.

Hope his helps

Cheers
JL
0
VIVEKANANDHAN_PERIASAMYAuthor Commented:
Nope you got my question wrong.

I don't want to find the cause of slow link,latency issue. I just want to know how of replication commands are getting  transferred from  publisher to distributor in a second.
And way to find out the details.

I don't only want to monitor the active transaction per second. I want to know history transaction speed( or you say can cummulative transaction replication command per second).

Is there any DMV's or perfmon counter to measure this metrics?
0
lcohanDatabase AnalystCommented:
"I just want to know how of replication commands are getting  transferred from  publisher to distributor..."

Did you checked "How Transactional Replication Works"?
http://technet.microsoft.com/en-us/library/ms151706(v=sql.105).aspx

This article may help with the " transaction speed":

"Determine data latency between Publisher and Subscriber in SQL Server Transactional Replication"

http://www.mssqltips.com/sqlservertip/2590/determine-data-latency-between-publisher-and-subscriber-in-sql-server-transactional-replication/

If you want rather to do it via dm_... views you can find them all here:

"Replication Related Dynamic Management Views"
http://technet.microsoft.com/en-us/library/ms176053(v=sql.105).aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.