October 27, 2011 at 9:57 pm
Comments posted to this topic are about the item SQL Server 2008 - Disabling Full Text Search
Thanks & Regards,
Nakul Vachhrajani.
http://nakulvachhrajani.com
Follow me on
Twitter: @sqltwins
October 27, 2011 at 9:58 pm
Good question, never heard about this. Thanks.
M&M
October 28, 2011 at 12:03 am
Great question, I didn't know this was the default.
Learned something on a Friday 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 28, 2011 at 2:37 am
Thanks for the question.
However, I'm curious about the discussion to follow, as I personally find the wording ambiguous 😉
In order to be able to carry out a (plain English) full text search, you have to set up a (MSDN speak) full-text catalog with at least one full-text index (see MSDN Getting Started with Full-Text Search).
In plain English: While any database created in SQL Server 2008 (and higher) is (MSDN speak) full-text enabled (please note: no search), use of this feature can only be made after performing certain steps. And if you drop the full-text index, no (plain English) full text search can be carried out (what I'd say qualifies as 'full text search is disabled').
So thanks again for the question and pointing towards the interesting wording approach by MSDN. 😎
October 28, 2011 at 2:44 am
Nice question, glad I received a point 🙂
But you can disable or Re-enable a Table for Full-Text Indexing 🙂
October 28, 2011 at 2:48 am
This was removed by the editor as SPAM
October 28, 2011 at 2:57 am
Although, like 71% (at this time) of the others, I got this wrong because I was thinking Full-text indexing on a table can be disable/re-enabled. The question, on re-reading, is unambiguous in that it quite clearly talks about full text search on a database.
Ah well... got me 😛
_____________________________________________________________________
[font="Comic Sans MS"]"The difficult tasks we do immediately, the impossible takes a little longer"[/font]
October 28, 2011 at 3:38 am
Good question, however the answer is a bit pedantic, so I'm going to be a bit pedantic in my comment. Whilst you can't disable full text search at the database level, you can achieve this in effect by disabling it at the table level, so if you do it on all tables, it is removed, is it not?:-)
October 28, 2011 at 3:52 am
ipounder (10/28/2011)
Good question, however the answer is a bit pedantic, so I'm going to be a bit pedantic in my comment. Whilst you can't disable full text search at the database level, you can achieve this in effect by disabling it at the table level, so if you do it on all tables, it is removed, is it not?:-)
I would say not... because if I then add a full text index to a table I can still do a full text search.
Whereas, in previous versions of SQL, if I'd disabled it at database level adding a full-text index would not result in the ability to full text search.
_____________________________________________________________________
[font="Comic Sans MS"]"The difficult tasks we do immediately, the impossible takes a little longer"[/font]
October 28, 2011 at 4:10 am
Wot DugyC sed. Fortunately I overrode my immediate impulse to get this one right!
October 28, 2011 at 4:29 am
good question!!! thanks!
October 28, 2011 at 4:32 am
Nice one, thanks
Iulian
October 28, 2011 at 8:29 am
hmmm...interesting question.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
October 28, 2011 at 8:35 am
good question - thanks!
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply