|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Monday, June 10, 2013 6:56 AM
Points: 1,282,
Visits: 1,613
|
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: 2 days ago @ 10:29 PM
Points: 2,178,
Visits: 3,599
|
|
Good question, never heard about this. Thanks.
Mohammed Moinudheen
|
|
|
|
|
SSCrazy Eights
        
Group: General Forum Members
Last Login: Yesterday @ 6:30 AM
Points: 9,410,
Visits: 6,495
|
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, May 28, 2013 1:34 AM
Points: 1,263,
Visits: 1,080
|
|
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.
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Monday, June 03, 2013 6:06 AM
Points: 388,
Visits: 296
|
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 3:51 AM
Points: 3,163,
Visits: 4,342
|
|
This is a good question, and I think the discussion to follow is going to be quite interesting.
____________________________________________ Space, the final frontier? not any more... All limits henceforth are self-imposed. “libera tute vulgaris ex”
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 1:49 AM
Points: 1,182,
Visits: 745
|
|
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
_____________________________________________________________________ "The difficult tasks we do immediately, the impossible takes a little longer"
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: 2 days ago @ 3:53 AM
Points: 1,051,
Visits: 125
|
|
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?
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 1:49 AM
Points: 1,182,
Visits: 745
|
|
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.
_____________________________________________________________________ "The difficult tasks we do immediately, the impossible takes a little longer"
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 4:01 AM
Points: 1,113,
Visits: 716
|
|
| Wot DugyC sed. Fortunately I overrode my immediate impulse to get this one right!
|
|
|
|