Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-04-20 : 09:56:06
|
| Sajit writes "I am currently using the spItemSearch02 Stored procedure written by Graz in my application to search for multiple keywords. I downloaded it from the article titled 'Searching on SQLTeam.com'. It worked like a dream untill the data increased considerably. Now i am often getting Timeout errors in my asp page when searching for just two key words!!. I had modified the stored procedure to further filter the data by passing additional search criterions, say like the 'User_ID' and 'Date Created' etc. I can post the etire storend procedure if needed. The tables are nicely indexed and normalised. Would there be any specific reason for the Procedure to slow down considerably as the number of rows in the table increases.I am a great admirer of SQLTEAM and use your suggestions and code snippets in my apps. keep up the good work.Regards,Sajit" |
|
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
Posted - 2004-04-20 : 09:56:06
|
| How many records are we talking about it? Remember it is doing multiple table scans -- one for each keyword. And it searching a text (or varchar) column while it's at it. I'm guessing it wouldn't scale real well. You'd probably need full-text indexing or some other type of indexing scheme to scale well. |
 |
|
|
|
|
|
Performance Issue on the Search Stored Procedure posted by Graz