cubedwellingslave
Programmer
Ok has anyone yet figured out the magic key to getting ODBC performance to come even close to MSSQL (we're using P.SQL 2000i SP3 on a Quad Xeon 2.4 Ghz w/ 2GB RAM)
Using the Btreive API would be a waste since the DB is going to be upgraded to MSSQL later this year, but the tools I'm working on can't wait, so I pretty much need to get ODBC working so I don't have to write this app twice.
We're experiencing the "10 seconds on SQL, 5 minutes on P.SQL" issue that seems pretty common.
TIA!
-sdf
PS: if anyone from Pervasive reads these boards:
1) Why the heck, when using the OLEDB driver, do stored procedures execute on the client? This makes writing stored procs that tie separate DB's together for consolidated reporting impossible.
2) SMP Support? I don't like seeing 3 procs sitting idle when CPU0 is pegged at 100% and queries are taking 5 mins to run...
Using the Btreive API would be a waste since the DB is going to be upgraded to MSSQL later this year, but the tools I'm working on can't wait, so I pretty much need to get ODBC working so I don't have to write this app twice.
We're experiencing the "10 seconds on SQL, 5 minutes on P.SQL" issue that seems pretty common.
TIA!
-sdf
PS: if anyone from Pervasive reads these boards:
1) Why the heck, when using the OLEDB driver, do stored procedures execute on the client? This makes writing stored procs that tie separate DB's together for consolidated reporting impossible.
2) SMP Support? I don't like seeing 3 procs sitting idle when CPU0 is pegged at 100% and queries are taking 5 mins to run...