High Traffic Site Infrastructure | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

High Traffic Site Infrastructure

Are there any folks here that have been involved in high traffic sites? We are wondering how people design infrastructure for heavy reads and heavy update sites. Do people have a separate "read section" and "update sections", then transactional replication maybe. Just would like some insight from people that have experience with this.

There are a many factors to be consider before designing setup for any demanding application: – Hardware: Need to be faster i.e faster disk 15k, dedicated RAID (10 etc), multiple CPU, fiber connectivity, max L3/ L4 cache, etc. Software: Need to be well-designed database keeping consideration of locking architecture in database. Another if you don’t need old data a proper database archiving planning, Tested indexes on tables and defragmentation activities, etc.
Yes, if your application has different modules for read and update. Can use SQL Transactional replication to distribute workload. Again, if your application is so huge like having thousand#%92s of transaction per second can design as per SQL Merge replication. Deepak Kumar –An eye for an eye and everyone shall be blind
any infrastructure specifics from personal experience with this?

<br />Choose best server for your database.. you need to findout workload before..<br /><br />IBM X440/ X445 and more ahead<br />DELL 6650<br />Unisys Aries 510/520 and more ahead <br />HP rx8620 [<img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ />]<br /><br /><br />I can’t say anything without knowing what work load your application will be having and what kinda work it gonna to do? and so many questions…<br /><br /><br /><br /><br /><br /><br />Deepak Kumar<br /><br />–An eye for an eye and everyone shall be blind
current: – 1 OLTP db
– 4 read db’s (site hits here only)
– 5 million reads / day.
– site data gets updated once daily (DTS)
but now we need to update frequently yo the site. DTS not longer good.

hardware for OLTP server
– mid-high end (4 cpu, 4gb, 4 i/o path) hardware for read servers
– mid-range (2 cpu, 2gb)
i am looking for sample infrastructure of other busy sites. – more so on how they keep the data updated.