woops sorry I see that 2005 my guess would be 2005 is optimized
for .net and the ajax where witango is so long in the tooth now it is
not. One would expect 6 to improve on this. You might try contact
witango support about this and about the expectation for 6 it is the
kind of question they should answer. I would CC sales also.
Let us know what you hear back or if you don't
--
Dan Stein MSN
FileMaker 7 Certified Developer
FileMaker 9 Certified Developer
Digital Software Solutions
303 W. Chestnut St
Souderton PA 18964
Land: 215-799-0192
Cell: 610-256-2843
Fax 215-799-0192 ( Call 1st)
FMP, WiTango,MSSQL, MySQL,PHP
d...@dss-db.com
www.dss-db.com
"When you are born, you cry and those who love you rejoice. And
if you
live your life as you should, when you die, you rejoice and those who
love you cry."
On Oct 6, 2009, at 9:44 AM, Ted Wolfley wrote:
Hi,
We created a simple ajax autocomplete retrieving name and company
from a sql server 2005 table on another server. We compared 2
different options.
Both servers are Windows 2003 32-bit
Using Witango 5.5, the query request took 528ms.
Using ASP.Net, the query request took 34 ms
The sql statement is the same for both queries
Wondering if someone could give an explanation why there is so much
difference in speed and is there a way to speed up the Witango query.
Ted Wolfley
Lead Internet and Database Programmer
The Ogden Group of Rochester
phone: (585) 321 1060 x23
fax: (585) 321 0043
t...@ogdengroup.com
www.ogdengroup.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
