i am using sql server 2000 can i use full text search on the view of a table..
No. SQL Server 2000 Full Text Search does not directly support Full Text Indexing of views. However, you can include Full Text queries in views, but not create Full Text Indexes on views in SQL Server 2000.
Related
I am new to Full Text Search of Sql server. Why I would create another Catalog beside the default one?
I actually don't understand how exactly catalog organize full text indices, I had impression that it is just like a schema to a table. please verify that to me.
Thanks
It appears that it is not possible to add a second Full Text catalog to the same table. On SQL Server 2008R2, once I've added a catalog, the button to add another is disabled:
You can add 2 eligible columns to the same catalog though:
More advice on FTS:
Database Journal - Setting up full text search: A step-by-step guide
MSDN - SQL Server Best Practices - Full Text Search
I want to find the name of full text search catalog on my SQL Server 2008 database. How can I do that using SQl Server Management Studio or TSQL. I tried using:
SELECT FullTextServiceProperty('IsFullTextInstalled')
and it returns 1.
This query will help:
select name, *
from sys.fulltext_catalogs
You can have more than one full-text search catalog, so the query will return all of them. The one that is default will have is_default = 1.
How to get started with Fulltext Search in SQL Server 2008
read these links:
SQL SERVER – 2008 – Creating Full Text Catalog and Full Text Search
Using Full Text Search in SQL Server 2008
Setting Up Full Text Search: A Step-by-step Guide
Full-Text Search (SQL Server)
SQL Server 2008 Full Text Search Best Practices from the SQL CAT Team
I would add those links from Simple Talk's web site:
Understanding Full-Text Indexing in SQL Server
SQL Server Full Text Search Language Features
SQL Server Full Text Search Language Features - Part 2
Does MySQL have an equalavent to SQL Servers "indexed view" functionality?
Is a view faster than a simple query?
What I'm specifically looking for is a way for MySQL to create a "view" that will return results faster than simply performing the underline view's query/sql.
An Indexed View is SQL Server terminology for a materialized view, which MySQL does not support.
You can either:
re-create a temporary table, populated with the desired columns, at a given interval
use an actual table, populated and indexed though again - there'd have to be a process to keep the data and indexes current
Is there anyway to add some custom stop words to SQL Server 2005?
I found the answer:
On SQL Server 2005:
On SQL 2005 they have the concept of "noise word lists". These are essentially the same thing, but they're stored as text files in the file system. These files have names like "noiseenu.txt" (U.S. English noise word text file) and are located in a subdirectory of your SQL Server instance directory (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\, for instance). You can edit it with any text editor and save again. I don't recall whether or not you need to bounce the service afterwards on 2005 (don't recall if the noiseword list is cached in memory, but you may as well bounce it to be sure). Then you have to rebuild your full-text indexes.
On SQL Server 2008:
You can create a custom stopword list on SQL 2008 the server will remove the stopwords at index time and when it parses your full-text search queries. All you have to do is specify that your full-text index use the custom stoplist.