New answers tagged full-text-search
1
You have to use DDL event groups that can be used to run a DDL trigger or an event notification, and also the Transact-SQL statements they cover.
Refer BOL for more details on what can be tracked.
I have posted an answer here for How to get notified when a deadlock occurs using Event notification. The concept is similar and can be applied to audit Full ...
5
Your comments note that you're specifically talking about full-text indexing.
You can indeed query the database while a full-text index is being created. Full text indexes are created in the background on SQL Server 2005, 2008, and 2008R2.
You can continue to query the database using the LIKE operator, although of course the queries won't be as fast as a ...
2
After a few days of fiddling around, I finally managed to get this done. Here is the code I ended up with, packed into a stored procedure. For this to work, I added another table, which just holds a document ID and its length in words.
ALTER PROCEDURE [dbo].[BuildIndexBM25]
-- default parameteres K1=> [1.2 - 2.0], B => [0.0 - 1.0], Weight => 3 ...
2
First of all, Welcome to stackexchange and thanks for your 1st Post.
To answer your questions :
if this process of reorganize the Full Text Catalog is done online or offline?
The reorganize process is Online, but is slower than Rebuild.
When the catalog reorganize is occurring the users will still be able to query the full text data?
Yes, but there ...
3
There are couple of things to consider :
backup and restore is the safest option that you can use for migration from SQL 2005 to 2012.
Refer here for more details of what you are experiencing.
Full text has undergone major chance in 2008 and up.
from BOL,
Attaching a SQL Server 2005 Database to SQL Server 2012
In SQL Server 2008 and later versions, a ...
0
stoplist can't be replicated but there is one ugly way to do it. Words in Stop lists are stored in sys.fulltext_stopwords . Using linked server you can query this table and compare it on secondary server . If there are any changes then run alter command on secondary to add\remove those changes from stoplist.
ALTER FULLTEXT STOPLIST YourStopLIstName ADD 'en' ...
1
That's not all that large of a table for full text indexing. When you hit hundreds of millions or billions of rows that where things that getting more complex.
As it is just setup the full text catalog and index to do auto population and auto change tracking (these are the defaults) and you'll be fine.
3
Full text in SQL Server should have no trouble keeping up with your workload. I currently support a full text index in SQL Sever that is approximately 500,000 rows with 125,000 rows being inserted and deleted everyday. Query load peaks at around 200 full text searches/sec. Response time it's fairly consistent in the .5 to 1.5 sec range.
...
Top 50 recent answers are included
