Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/27/2012 in all areas

  1. You could also use something like this and then parse out the X and Y values from it. LeftValues ( ExecuteSQL ( " SELECT Count (c_date) as thedate, Region FROM eqs7day_M1 WHERE c_date >= ? AND c_date <= ? GROUP BY Region ORDER BY thedate DESC " ; "" ; ""; global::dateStart; global::dateEnd ) ; 5 ) or LeftValues ( ExecuteSQL ( " SELECT Count (c_date) as thedate, Region FROM eqs7day_M1 WHERE c_date BETWEEN ? AND ? GROUP BY Region ORDER BY thedate DESC " ; "" ; ""; global::dateStart; global::dateEnd ) ; 5 )
    1 point
  2. I agree with Markus - I have the same experience. In the past my company invested a lot of money to improve our server hardware, but we never saw the solution's performance improved by more than 20-30 % by that. We aso tried to go the long-term optimization path Markus is suggesting, but it was a lot of work and lot of guessing. Last year I discovered that the most efficient way to improve performance of our solution was to identify the real bottleneck (learn more about it at http://FMBench.com/bottleneck) and optimize just the bottleneck. However, sometimes it's hard to find the bott
    1 point
This leaderboard is set to Los Angeles/GMT-07:00
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.