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 |
|
csphard
Posting Yak Master
113 Posts |
Posted - 2003-12-30 : 17:52:58
|
| My users want to develop a key word search screen. They will provide a list of questions and answers. I have questions about how the table should be developed. Should i have a field with the text information in it and query it. Or should i have a key word field where i put the text that i think the user will use to search for. I'm questioning how the table should be set up. If there are any ideals i would appreciate it. |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2003-12-30 : 18:35:34
|
| Take a look at this article. I've used this on a large VARCHAR field, and it worked pretty well. If you create a new field of "keywords" that's one more field you have to make sure is "rebuilt" every time a new record is added or edited. You could also try a hybrid aproach where you have a keyword column and saerch both the full text and the keyword table.http://www.sqlteam.com/item.asp?ItemID=5857Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2003-12-31 : 00:31:37
|
| Have you considered Full-text indexing on the columns? This will give you certain advantages like fuzzy searches and automatic ranking, not to mention it will save you the headache of creating a keyword table which needs to be updated constantly. If you implement something like this yourself with a keyword table, you will need to worry about "near-misses" due to forms of verbs, special characters such as commas and hyphens etc. all of which can skew the search results.Look at the Full-text indexing topic in the Books Online for more information.OS |
 |
|
|
|
|
|