SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


OLTP process question


OLTP process question

Author
Message
sandie_zarate
sandie_zarate
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 37
If our processes run every 2 minutes on 3 DBs simultaneously, everything is fine... why are we encountering problems if we run our processes every 2 minutes on more than 3 DBs? Assumption: We have more or less 20,000 SQL statements to execute for each DB every 2 minutes?
Our goal is to finish the process within 2 minutes for 40 DBs and more.

Any recommendations to improve performance or what to check that cause it to slow down when we increase the # of database to process? Will using SAN disk be of help?

- SQL Server 2008 R2
- data and log files are currently located in drive C:
- bytes per cluster on drive C:is set to 4kb.
Eirikur Eiriksson
Eirikur Eiriksson
SSC-Dedicated
SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)

Group: General Forum Members
Points: 39918 Visits: 19443
sandie_zarate (8/14/2014)
If our processes run every 2 minutes on 3 DBs simultaneously, everything is fine... why are we encountering problems if we run our processes every 2 minutes on more than 3 DBs? Assumption: We have more or less 20,000 SQL statements to execute for each DB every 2 minutes?
Our goal is to finish the process within 2 minutes for 40 DBs and more.

Any recommendations to improve performance or what to check that cause it to slow down when we increase the # of database to process? Will using SAN disk be of help?

- SQL Server 2008 R2
- data and log files are currently located in drive C:
- bytes per cluster on drive C:is set to 4kb.


First priority would be separating the data from the OS activity, given the C: is the OS / page file drive. After that one can start gathering statistics and ironing out other bottlenecks, the average of 170 statements per second doesn't sound much but it mounts up, 40 dbs and its approaching 7000 per second.
Cool
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search