Reply to: FullText Search - SQL Server

[TheFaQQer]

Ah yes, except wild cards did not work.

Really? Because you said earlier that wildcards did work:

I did actually mean

Like '%attrn'

works

[suityou01]

Are you aware that you need wildcard when searching for something that's not a stem?

Since Att isn't a stem of Attrn, you need to use a wildcard.

Ah yes, except wild cards did not work.

[TheFaQQer]

Sorry LM, no you didn't. Others did.

I have read your link and understand what you are telling me, finally.

Are you aware that you need wildcard when searching for something that's not a stem?

Since Att isn't a stem of Attrn, you need to use a wildcard.

[fannyadams]

Can you post the exact syntax you used for the wildcard? It should work. Did you have the double layer of quotes?

https://blogs.msdn.microsoft.com/sql...l-text-search/

[LondonManc]

Sorry LM, no you didn't. Others did.

I have read your link and understand what you are telling me, finally.

Finally.

[MrMarkyMark]

Sorry LM, no you didn't. Others did.

I have read your link and understand what you are telling me, finally.

Penny....Finally.........Drops

[suityou01]

Because you either need a "*" wildcard or to include something extra like FORMSOF, INFLECTIONAL and / or FREETEXT rather than just CONTAINS.

That's the opposite of what you said

What's syntax are you using for your wildcard match?

I've not recommended the bloody wildcard.

I'm telling you that Attrn is not a natural stem from Att so you won't get a result, which is the correct behaviour.

To get Attrn in your result set, you'd have to use like %Att% in your where clause instead.

Sorry LM, no you didn't. Others did.

I have read your link and understand what you are telling me, finally.

[LondonManc]

Yes but the wildcard doesn't work. I'm sure I mentioned this before.

I've not recommended the bloody wildcard.

I'm telling you that Attrn is not a natural stem from Att so you won't get a result, which is the correct behaviour.

To get Attrn in your result set, you'd have to use like %Att% in your where clause instead.

[suityou01]

If he reads the blog post that I linked to, rather than waiting to be spoonfed the answer, he'd know that by now.

Yes but the wildcard doesn't work. I'm sure I mentioned this before.

[LondonManc]

It's to do with stemming.

Grab a coffee and have a read through this:
https://blogs.msdn.microsoft.com/sql...sing-contains/

I've not touched fts for years, but it is basically looking for words, without wildcards it works off the stems of whole words, so "story" or "stories" are the same, as are tenses such as "going" and "gone". This used to show up in Sharepoint, where searches for, say, product IDs unless fully qualified failed miserably.

If he reads the blog post that I linked to, rather than waiting to be spoonfed the answer, he'd know that by now.

[BigRed]

I've not touched fts for years, but it is basically looking for words, without wildcards it works off the stems of whole words, so "story" or "stories" are the same, as are tenses such as "going" and "gone". This used to show up in Sharepoint, where searches for, say, product IDs unless fully qualified failed miserably.

[fannyadams]

Not getting it.

How is "Exactlymatchinstri' a word, but 'Exactlymatchingstring' isn't?

That's the opposite of what you said

What's syntax are you using for your wildcard match?

And no, sadly a wildcard doesn't make any difference. Still nada.

Thanks for trying chaps.

Edit : I just got this to work.

SELECT * FROM MyTable WHERE Contains(MyField,'Exactlymatchingstring')

This works. But

SELECT * FROM MyTable WHERE Contains(MyField,'Exactlymatchi')

does not work.

[MrMarkyMark]

And no, sadly a wildcard doesn't make any difference. Still nada.

Thanks for trying chaps.

Edit : I just got this to work.

SELECT * FROM MyTable WHERE Contains(MyField,'Exactlymatchingstring')

This works. But

SELECT * FROM MyTable WHERE Contains(MyField,'Exactlymatchi')

does not work.

Worth as much as you have paid for it.

I trust this is for some hobby project and no one is paying for your SQL Server "expertise"

[TheFaQQer]

Not getting it.

How is "Exactlymatchinstri' a word, but 'Exactlymatchingstring' isn't?

Because you either need a "*" wildcard or to include something extra like FORMSOF, INFLECTIONAL and / or FREETEXT rather than just CONTAINS.

[LondonManc]

Not getting it.

How is "Exactlymatchinstri' a word, but 'Exactlymatchingstring' isn't?

It's to do with stemming.

Grab a coffee and have a read through this:
https://blogs.msdn.microsoft.com/sql...sing-contains/