How fast is SQL Replication?

I have a large SQL database that gets a lot of very fast insertions - sometimes up to 250 per second - possibly more.

The machine is pretty powerful (6 core XEON, hyperthreaded, 32Gb RAM) - and I have a duplicate on the same network. My question is - how fast should this sort of database be able to replicate to a second server? The data is financial, and time-sensitive - so a few seconds delay is not acceptable; I might just about get away with a second.

The servers are both running MS SQL 2008, 64 Bit edition - one as Standard Edition (publishing), and the other is Web Edition (subscriber).

LVL 4
Fuzzyfish1000Asked:
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.

lcohanDatabase AnalystCommented:
0
lcohanDatabase AnalystCommented:
Honestly, in my opinion if "The data is financial, and time-sensitive - so a few seconds delay is not acceptable" you should look at updating your App/Systems to write data directly in both tadatabse - it's development/goding/testing indeed but this way it goes directly where it should without any delay.

Alternative to that but still coding is to have triggers on the source tables and populate data in target financial tables through linked sql server if both servers are on the same network.
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
Anthony PerkinsCommented:
>>The data is financial, and time-sensitive - so a few seconds delay is not acceptable; I might just about get away with a second. <<
You are out of luck.  Replication is not for you.

0
Fuzzyfish1000Author Commented:
Thanks chaps. I think we've come to that conclusion; Replication isn't a viable option; and we're looking at distributing the data via linked SQL servers and triggers.
0
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

From novice to tech pro — start learning today.