Post reply

Full Text Search - where are system stoplists stored?

  • August 20, 2011 at 5:52 pm

    #255905

    Comments posted to this topic are about the item Full Text Search - where are system stoplists stored?

    Thanks & Regards,
    Nakul Vachhrajani.
    http://nakulvachhrajani.com

    Follow me on
    Twitter: @sqltwins

  • August 20, 2011 at 5:55 pm

    #1371098

    Surprised at the numbers (3 out of 4 incorrect), for what is a rather simple question.

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • August 20, 2011 at 7:03 pm

    #1371104

    A nice easy one for Monday morning.

    I was somewhat surprised to see it before 0100 BST on Sunday, though.

    Tom

  • August 20, 2011 at 7:05 pm

    #1371105

    A nice easy one for Monday morning.

    I was somewhat surprised to see it before 0100 BST on Sunday, though.

    EDIT: Why are there two of this? Is it a consequence of looped time? (See the post two further down.) Will this edit affect both copies?

    Tom

  • August 21, 2011 at 7:13 am

    #1371153

    Nice question Nakul 🙂

  • August 21, 2011 at 2:02 pm

    #1371195

    Tom.Thomson (8/20/2011)

    A nice easy one for Monday morning.

    I was somewhat surprised to see it before 0100 BST on Sunday, though.

    Tom you must have been accessing the QOD when I had it open using the undocumented command DBCC TimeWarp.

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • August 22, 2011 at 2:09 am

    #1371281

    Thanks for the great question, learning something new everyday and today is no exception 😀

    _____________________________________________________________________
    [font="Comic Sans MS"]"The difficult tasks we do immediately, the impossible takes a little longer"[/font]

  • August 22, 2011 at 5:28 am

    #1371348

    Good question, thanks.

    http://brittcluff.blogspot.com/

  • August 22, 2011 at 5:35 am

    #1371350

    Thanks for the question!

    I'm curious about the terminology though. The previously used "noise words" did a good job at conveying the meaning of what was being represented. Seems like "stopwords" is less clear as to purpose. Can anyone enlighten me as to why this terminology was chosen?

    [font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
    Connect to me on LinkedIn

  • August 22, 2011 at 6:04 am

    #1371357

    A nice easy one for Monday morning.

  • August 22, 2011 at 7:45 am

    #1371408

    Good question, got it wrong.

    Was it the same in 2005? I thought that we configured the stopwords and thesaurus via text files back in 2005, which is the last time I played with FT search. I remembered reading that there were some major improvements to FT for Denali, so I figured that not much had changed in 2008.

    ah well.


    --Mark Tassin
    MCITP - SQL Server DBA
    Proud member of the Anti-RBAR alliance.
    For help with Performance click this link[/url]
    For tips on how to post your problems[/url]

  • August 22, 2011 at 8:14 am

    #1371427

    Thanks for the question!

    -Dan

  • August 22, 2011 at 8:16 am

    #1371431

    Thomas Abraham (8/22/2011)

    Thanks for the question!

    I'm curious about the terminology though. The previously used "noise words" did a good job at conveying the meaning of what was being represented. Seems like "stopwords" is less clear as to purpose. Can anyone enlighten me as to why this terminology was chosen?

    I totally agree on the term... Noise words makes sense to me, stop words not so much...

    -Dan

  • August 22, 2011 at 9:10 am

    #1371469

    great question!!! thanks!

    [font="Times New Roman"]rfr.ferrari[/font]
    DBA - SQL Server 2008
    MCITP | MCTS

    remember is live or suffer twice!
    the period you fastest growing is the most difficult period of your life!

  • August 22, 2011 at 9:30 am

    #1371484

    skrilla99 (8/22/2011)

    Thomas Abraham (8/22/2011)

    Thanks for the question!

    I'm curious about the terminology though. The previously used "noise words" did a good job at conveying the meaning of what was being represented. Seems like "stopwords" is less clear as to purpose. Can anyone enlighten me as to why this terminology was chosen?

    I totally agree on the term... Noise words makes sense to me, stop words not so much...

    -Dan

    Ditto. Terminology is a bit confusing. I guess it was used to mean "stop creating the full text index when you hit these words" of course the index creation does not actually stop but instead just discards those words that exist in the stoplist. I like noisewords better because I liken it to cleaning out the noise from a recording. For instance if you were transferring an LP to CD you would want to remove as much of the noise from the recording as possible (pops, fuzziness, scratches). This would result in a more optimized recording just as a full text index is more optimized for searches when the noisewords are removed.

Viewing 15 posts - 1 through 15 (of 19 total)

You must be logged in to reply to this topic. Login to reply

Cookies on SQLServerCentral

This website stores cookies on your computer.

These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.

To find out more about the cookies we use, see our Privacy Policy