Prev: SQLSERVER SqlListTables
Next: Linear Owner Alignment
From: Darmadi on 2 Dec 2009 21:09 Hi Steve, > Nope - you set up a timer (200-300ms) to send a query between each > keystroke. Sending query everytime keystoke, does it impact the performance of SQL-Server? My logical, sending a query, then the server will querying the data that match the query statement (maybe 1000 records), then sending query again (maybe 500 records), is it slow, cause we need to wait the process from server? Regards, Darmadi "Stephen Quinn" <stevejqNO(a)bigpondSPAM.net.au> wrote in message news:dUERm.59637$ze1.27566(a)news-server.bigpond.net.au... > Darmadi > >> Completely different with SQL, that user must finish typing, then we >> create a SQL statement, then showing the quering data. > > Nope - you set up a timer (200-300ms) to send a query between each > keystroke. > > CYA > Steve >
From: Stephen Quinn on 2 Dec 2009 22:38 Darmadi > (maybe 500 records), is it slow, cause we need to wait the process from > server? No idea if it's slow or not - experiment with your code and typical search criteria. I was just pointing out that you do not need to wait for the user to enter a full set of criteria before starting to search. CYA Steve
From: Geoff Schaller on 2 Dec 2009 23:49
Not here. Only 50,000+ rows is slow "Darmadi" <support(a)gfsoftindo.com> wrote in message news:hf76j0$p92$1(a)aioe.org: > Hi Steve, > > > > Nope - you set up a timer (200-300ms) to send a query between each > > keystroke. > > > Sending query everytime keystoke, does it impact the performance of > SQL-Server? > My logical, sending a query, then the server will querying the data that > match the query statement (maybe 1000 records), then sending query again > (maybe 500 records), is it slow, cause we need to wait the process from > server? > > Regards, > Darmadi > > > "Stephen Quinn" <stevejqNO(a)bigpondSPAM.net.au> wrote in message > news:dUERm.59637$ze1.27566(a)news-server.bigpond.net.au... > > > Darmadi > > > > >> Completely different with SQL, that user must finish typing, then we > >> create a SQL statement, then showing the quering data. > > > > > Nope - you set up a timer (200-300ms) to send a query between each > > keystroke. > > > > CYA > > Steve > > |