Wow big difference, but your results in half. I had to use the SQL Search page for someone because the page was timing out. The SQL Search page is great.
Glad you guys like it . It was fun seeing how much it improved the performance of the original file. Of course, it only works for SQL Server (though probably it could work for Access as well), but I had more liberty than the original developers, who have to make it work with MySQL as well (and I am MySQL free !).
Yup. I've been happy with it since he released it. My queries would burn into timeouts, now they don't time out and finish in half the time. Rui rules!
It's not that the queries were timing out, it is that it sucks all the cpu. I still don't think the new one fixed it. I am going to have to find a way to limit cpu usage per process or something.
Still goes to 100% on searches. Any way to limit this to say...only go to 50% or so for the search function? I do not know why it does it. You guys say it doesn't max out your SQL server on a search?
no it doesn't and as far as I know you can;t limit SQL procesor usage other than to tell it how many processors to use, have your tried profiling to see if you need any new indexes creating ?
Yes I have profiled twice now. I am thinking that it is something to do with the database because even on a different sql server it does the same thing. I thought I read somewhere that you could limit the amount of cpu that the highest process could use.
Sorry to bring this back to the top again. ruirib, can you show me which query is doing the actual search on your search page? I wan't to run it in SQL query analizer to try figure out my problem. Need to see what is taking so much cpu time.
If you look at my code, you will find at line# 446 the opening of the recordset with the variable strFinalSql, which contains the SQL for the search in the DB. Response.write it and use it.
The process of building the SQL is a bit complex and the contents can vary on many things. That's why I think this is the best strategy for your purposes.
Topic Locked
Posted - 29 October 2003 : 12:40:42
. It was fun seeing how much it improved the performance of the original file. Of course, it only works for SQL Server (though probably it could work for Access as well), but I had more liberty than the original developers, who have to make it work with MySQL as well (and I am MySQL free 
!).
