Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using SQL Server 2000 and ASP.Net with c# for making a search engine.
I want to refine the results obtained from a search without making server connections again and again due to speed factor.
How can I make my search faster? How can I make fewer connections?
As Matthew alluded to, your two connection points are the HTTP request from the client (web browser) to the server (web server), and the connection from the web server to the sql server.
The connection from the web server to the sql server costs very little in the whole client-server-sql-server-client trip. So one would assume you are talking about the browser-to-webserver connection. Only way to avoid that is to dump the entire database (or at least the unfiltered pool of records one can query) to the browser and do your filtering client-side – which is an INCREDIBLY !!BAD!! IDEA.
So my suggestion would be to stop fretting, write the application as you normally would, and if things are looking slow when you are done then you can start looking for where the slowness is comming from – instead of trying to guess (and probably be wrong) before there’s even an issue.