September 12, 2008 at 1:09 pm
Maybe I'm missing out on some subtle definition, but it seems to me the last should be a correct option also.
I went to http://technet.microsoft.com/en-us/library/ms142551.aspx
and found the following
"Creating a Stoplist
You can create a stoplist in any of the following ways:
-Uploading the system-supplied stoplist in the database. SQL Server ships with a system stoplist that contains the most commonly used stopwords for each supported language, that is for every language that is associated with given word breakers by default. The system stoplist contains common stopwords for all supported languages. You can copy the system stoplist, and customize your copy by adding and removing stopwords.
The system stoplist is installed in the Resourcedatabase.
-Creating your own stoplist, and then adding stopwords to it for any language that you specify. You can also drop stopwords from your stoplist when necessary.
-Uploading an existing stoplist from any other database into the current database and then adding and dropping stopwords as necessary."
This last option seems to me to mean that you could have a dictionary file as a source database.
September 12, 2008 at 3:54 pm
The last option says "uploading an existing stoplist", not "uploading an existing dictionary file".
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 15, 2008 at 1:02 am
Question is correct.
February 24, 2015 at 3:09 am
Question which is easy to answer if you had already to create a stoplist. I had to dive deeply in my own memory as I faced this problem when I tested full-text with my SQL Server 2008 Developer around 7 years ago.
Nice question with no traps . Maybe 2 points are a too big value , except for people having used rarely this topic.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply