October 26, 2017 at 1:13 am
Hi everybody,
in my next project (asp.net web api on IIS) i have to manage many read - update - insert data in sql server 2012, about 10 http calls per second
in 1 call i have to :
1 ) read table [1], select with where in Pk, (it's possible to cache this table and update every 5 minutes)
2) read table [2] , compare data at 1), and decite to Update record in table [2] or insert data in table [2]. (not possible to cache)
Each operation is fast, but i have 10 request per second, so i have open and close connection 10 times for second.
Is Sql Server the best solution for my problem ?
i can't work in memory because iis can recycle application and i loose the data
xml file (or txt etc.) is better (fastest) solution ?
thank you.
October 26, 2017 at 5:58 am
SQL Server can easily handle this, with proper design, coding and indexing, then it can handle tens of thousands of transactions per second, 10 is absolutely nothing really!
😎
Use indexing rather than home made caching, the latter will have a much larger overhead.
Construct the code in the way that it will use index seeks rather than scans.
Post the incoming data structure and the destination schema structure with some sample data for further advice.
October 26, 2017 at 9:24 am
I have worked on numerous SQL Server systems with > ten thousand queries per second (on STANDARD edition), and one system, also Standard, that would occasionally touch over 100K/sec.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply