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 |
scripter
Starting Member
49 Posts |
Posted - 2007-05-28 : 20:45:03
|
I am building a generic job site and well I have hit a speed bump. I need to store resumes in the database to be searched on. Well what is the best way to store these full text resumes? so that they can be easily searched on?SQL 2005 |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-05-28 : 21:19:02
|
You can store them in nvarchar(max) column and use full text index do search. |
 |
|
Kristen
Test
22859 Posts |
Posted - 2007-05-29 : 04:43:21
|
full text index is probably best.We have encountered blocking/deadlocks when the Full text index updates but other than that its a) fast and b) uses root words and stuff to broaden the search.Alternative is to "split" the Resumes into individual words, maybe remove the "noise words", and then store the individual words in a Keywords table, and search using that.Searching usingSELECT ...FROM MyTableWHERE MyResume LIKE '%FirstWord%"AND MyResume LIKE '%SecondWord%"will run like a snail!Kristen |
 |
|
|
|
|