Skip to main content

Full-Text index in SQL Server

Full-Text index
Full-Text search supports to full-text queries against to character-based data. These types of queries can include words and phrases as well as multiple forms of a word or phrase. To support full-text queries, full-text indexes must be implemented on the columns referenced in the query. The columns can be configured with character data types (such as char and varchar) or with binary data types (such as varbinary and image).
The full-text index breaks the column into tokens and these tokens make up the index data. Before creating a full-text index you must create the full-text catalog which stored the full-text index data. A full-text catalog can contain many indexes but a full-text index can only be part of one catalog.  Also, only one full-text index can be created on each table. The full-text index is not updated like as it is regular indexes. Populating full-text indexes can be resource intensive so there are more options that let you control when they are updated. 

The 3 different options are:
1.     Full population
2.     Automatic or manual population based on change tracking
3.     Incremental population based on a timestamp

Benefits of Full-Text Index
The clustered and non-clustered indexes are not supported for any of the Large Object (LOB) data-types. Full-text indexes can be created on LOB data-type columns like TEXT, VARCHAR (MAX), IMAGE, VARBINARY (MAX) (it can also index CHAR and VARCHAR column types).
How to create a full-text index?
Before creating a full-text index we need some required setup. First, we create the full-text catalog for their storage. Catalog name must be unique across all databases on the server. Using the following script we can create the full-text catalog


After creating the full-text catalog we can the full-text index. There are two options we can add when creating a full-text index
1-        Key Index
2-        Stoplist
For creating full-text index a table should have a unique key and KEY INDEX index_name is the name of the unique key index on table_name. The KEY INDEX must be a unique, single-key, non-nullable column.

Note: Select the smallest unique key index for the full-text unique key. For the best performance, we recommend an integer data type for the full-text key.
Use the following script to create full-text index.

CREATE FULLTEXT INDEX ON Inventory.Item(ItemSummary)
KEY INDEX PK_Item_ItemsNode

Popular posts from this blog

Merge and Merge join transformation in SSIS

Using Merge Transformation we can combine two sorted data-set into single data-set basically Merge Transformation used to combines rows from two sorted data flows into one sorted data flow. Following tasks you may perform using Merge Transformation: 1.Suppose we have a scenario like, we need to merge data from a database table and excel means we want to merge data from two different data sources. For such type of scenario, you can use Merge Transformation. 2.If we want to merge data from two same structured tables but exists two different servers. 3.Sometimes we get an error due to data in a row, after correcting errors in the data we can re-merge rows easily. See below explanations may help you to understand Merge Transformation: I do evaluate here, you already know about the data source, data conversion, data flow, task flow, control flow etc. Note:Before Merge transformation, we need to sort the data using Sort Transformation. After sorting data add data path to Merge…

Add day to ISODate in MongoDB

We can use $add operator to add days in ISODate in mongodb, $add is the Arithmetic Aggregation Operator which adds number and date in mongodb.

{ $add: [ <expression1>, <expression2>, ... ] }

Note:  If one of the argument is date $add operator treats to other arguments as milliseconds to add to the date.
Example: Suppose we have a Test collection as below.

{"Title" : "Add day to ISODate in MongoBD","CreatedDate" : ISODate("2016-07-07T08:00:00.000Z")}

Query to add 2 days in CreatedDate

db.Test.aggregate([      { $project: { Title: 1, AddedDate: { $add: [ "$CreatedDate", 2*24*60*60000 ] } } }    ])


{ "_id" : ObjectId("579a1567ac1b3f3732483de0"), "Title" : "Add day to ISODate in MongoBD", "AddedDate" : ISODate("2016-07-09T08:00:00.000Z") }

Note: As mentioned in above note we have to convert days in millisecond because $add operator treat to other arg…

What is difference between UNION and UNION ALL in SQL Server

We use UNION and UNION ALL operator to combine multiple results set into one result set.
UNION operator is used to combining multiple results set into one result set but removes any duplicate rows. Basically, UNION is used to performing a DISTINCT operation across all columns in the result set. UNION operator has the extra overhead of removing duplicate rows and sorting result.
UNION ALL operator use to combine multiple results set into one result set but it does not remove any duplicate result. Actually, this does not remove duplicate rows so it is faster than the UNION operator. If you want to combine multiple results and without duplicate records then use UNION otherwise UNION ALL is better.
Following some rules for using UNION/UNION ALL operator
1.The number of the column should be the same in the query's when you want to combine them. 2.The column should be of the same data type. 3.ORDER BY clause can be applied to the overall result set not within each result set.
4.Column name of …