Hi, I'm encountering great difficult in ASA9 to SA12 migration. Generally I notice that many (new) automatism don't works well, in our scenarios. For example, today, I've discovered "Multiprogram Level" and, in my scenario, it places in "unscheduled request queue", a request without any really server critical status ! So, now, I'm managing "-gn" server option. Query optimization, also, works worst then on ASA9 ..... My question is: How can I set Sa12 to work as ASA9, WITHOUT any particular optimizazion ?? Please I need a simple efficient DB server .... not a black box that block request. Thanks.
asked 04 Jun '12, 07:44
I am skeptical that the new automatic multiprogramming level support is what is at the root of your performance issues. As Volker stated above, you can always turn it off, if you like, to go back to ASA9 behaviour. However, by default, v12's automatic support starts with 20 threads - you can set the -gnl value to 20 as well to prevent the pool from constricting too much if the server becomes idle, and hence the pool will not go below 20 (the ASA9 default).
There are LOTS of differences between ASA9 and SA v12 servers. I have outlined a partial list here. That list includes a new data store, new index type, new I/O cost model, various changes to statistics gathering and histograms, new query execution techniques, and so on - unsurprising since we've added a lot to the server in the last 8 years.
I suggest you open a support case so that someone in support can help you work out solutions or workarounds to these issues.
answered 04 Jun '12, 17:02
I love a good rant!
If you want to try V12 again, make sure you're using a recent EBF (build) of 12.0.1... then try using the Foxhound database monitor to see what's going on.
The free Evaluation Edition of Foxhound is still available (until Version 2 is released, and then the monthly Rental Edition will replace the Evaluation Edition).
answered 04 Jun '12, 12:28