As long as you've managed fulltext index on your table
DECLARE @searchWord [nvarchar](128)
SET @searchWord = N'POINT (-97.990837 26.159519)'
FROM .[qanda].[fulltextSearchable] WHERE
Otherwise you'll get an error like this:
Msg 7601, Level 16, State 2, Line 6
Cannot use a CONTAINS or FREETEXT predicate on table or indexed view .[qanda].[fulltextSearchable] because it is not full-text indexed.
If the index is not set up correctly, you'll probably have encountered a message like this:
Msg 9928, Level 16, State 1, Line 1
Computed column 'GeogCol2' cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed column.
Or something completely different:
Msg 7653, Level 16, State 1, Line 1
'--------' is not a valid index to enforce a full-text search key. A full-text search key must be a unique, non-nullable, single-column index which is not offline, is not defined on a non-deterministic or imprecise nonpersisted computed column, does not have a filter, and has maximum size of 900 bytes. Choose another index for the full-text key.
And if competancy is determined by something like a spelling error in the code, you might even encounter an error like:
Msg 7609, Level 17, State 5, Line 1
Full-Text Search is not installed, or a full-text component cannot be loaded.
Skip all of the above to verify quickly whether FULL-TEXT SEARCH is even installed:
EXEC sp_fulltext_service @action='upgrade_option', @value=1;
Except for the fact that the example I use here is oogusbay because geometry type is not full-text searchable by definition, using this form is expedient to understanding so I'll continue it here:
CREATE FULLTEXT CATALOG rwood_131_FTCat
CREATE UNIQUE INDEX ui_131 ON .[qanda].[fulltextSearchable](idx)
CREATE FULLTEXT INDEX ON .[qanda].[fulltextSearchable](
KEY INDEX ui_131 ON rwood_131_FTCat
WITH CHANGE_TRACKING AUTO
SELECT * FROM sys.fulltext_indexes
That last bit should do the trick. That is, if you've managed to install FULL-TEXT SEARCH in the beginning.