Full Text Indexing Option Disabled

i can again/still/no longer manage full-text indexes on SQL Server.
i'm logged on locally to my server, as an administrator. EM is set to poll
the server.
Has anyone written a gui to manage SQL Server free-text indexing?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ian Boyd" <admin@.SWIFTPA.NET> wrote in message
news:uG7DGLVXHHA.4520@.TK2MSFTNGP06.phx.gbl...
>i can again/still/no longer manage full-text indexes on SQL Server.
> i'm logged on locally to my server, as an administrator. EM is set to poll
> the server.
>
> Has anyone written a gui to manage SQL Server free-text indexing?
>
|||Have you tried this? It works for me every time.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlftzwiz.exe
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ian Boyd" <admin@.SWIFTPA.NET> wrote in message
news:uG7DGLVXHHA.4520@.TK2MSFTNGP06.phx.gbl...
>i can again/still/no longer manage full-text indexes on SQL Server.
> i'm logged on locally to my server, as an administrator. EM is set to poll
> the server.
>
> Has anyone written a gui to manage SQL Server free-text indexing?
>
|||> Have you tried this?>

> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlftzwiz.exe
Do you know which tool is used to maintain a full-text catalog / enable
disable table / start stop automatic-change tracking / start top incremental
population / start stop full population / see what databases/tables/columns
are being FT indexed / view/edit the work breaker set on a column / etc?
|||Under the covers some procs are used in SQL 2000, in SQL 2005 its moved into
the engine.
In SQL 2000 in some of the earlier versions you could use some of the com
components to manage parts of it. Have a look at ssadmin.vbs in
C:\Program Files\Common Files\System\MSSearch\Bin
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ian Boyd" <ian.msnews010@.avatopia.com> wrote in message
news:ONMJiglYHHA.2320@.TK2MSFTNGP03.phx.gbl...
>
> Do you know which tool is used to maintain a full-text catalog / enable
> disable table / start stop automatic-change tracking / start top
> incremental population / start stop full population / see what
> databases/tables/columns are being FT indexed / view/edit the work breaker
> set on a column / etc?
>

Full text indexes files missing?

I have a full text index...in the properties of the index the path
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.
They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegro ups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>

Full text indexes files missing?

I have a full text index...in the properties of the index the path
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegroups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>

Full text indexes files missing?

I have a full text index...in the properties of the index the path
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegroups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>

full text incremental population

Hi!
Is there any possibility to populate indexes for inserted rows only
(or not to updated rows)
Regards
MaxOn Apr 4, 10:27 am, maxl...@.gmail.com wrote:
> Hi!
> Is there any possibility to populate indexes for inserted rows only
> (or not to updated rows)
> Regards
> Max
pls... if anyone has came up with same problem. share your knowledge

full text incremental population

Hi!
Is there any possibility to populate indexes for inserted rows only
(or not to updated rows)
Regards
Max
On Apr 4, 10:27 am, maxl...@.gmail.com wrote:
> Hi!
> Is there any possibility to populate indexes for inserted rows only
> (or not to updated rows)
> Regards
> Max
pls... if anyone has came up with same problem. share your knowledge

Full Text computation eats too much CPU

Hi,
we are using fulltext indexes computation on Production Server.
MSSEARCH eats between 20 % and 40% in a regular manner.
It picks up to 40% then goes down to zero but some secondes later will climb
again to 20 and up to 40%
We are using System SP sp_fulltext_catalog on a main table with 2 millions
rows
and one NVarchar(255) column on which the FT Index is based.
We are searching ways to :
(1) limit CPU took by MSSEARCH
(2) allow FT computation only during a BATCH period not involving User
Activity and Perf degradation.
Many Thanks
Jean-Marc,
The CPU usage you are seeing is normal and expected behavior for the
MSSearch service during FT Indexing and some type of FT Search processing.
Specifically, for FT Indexing during the Shadow Merge and after an
Incremental or Full Population's Master Merge.
Does your production server support more than one CPU? If so, you can also
use the following command prompt command on the server to set the MSSearch
service to one CPU:
at <current_time+1_min> /interactive taskmgr.exe
and then use sp_configure to set SQL Server to use the other CPU to avoid
the MSSearch service from affecting your normal SQL Server processing. If
your production server does not support multiple CPU's, you can use the
sp_fulltext_service 'resource_usage' <value> and set <value> to 1
(background) as the default is 3 and the max is 5. This will reduce the
performance level of the MSSearch service and therefore reduce the FT
Indexing and FT Search performance levels.
Regards,
John
"Jean-Marc PUGIN" <jmpugin@.mobileworkers.com> wrote in message
news:u#zYJ6W0EHA.2540@.TK2MSFTNGP09.phx.gbl...
> Hi,
> we are using fulltext indexes computation on Production Server.
> MSSEARCH eats between 20 % and 40% in a regular manner.
> It picks up to 40% then goes down to zero but some secondes later will
climb
> again to 20 and up to 40%
> We are using System SP sp_fulltext_catalog on a main table with 2
millions
> rows
> and one NVarchar(255) column on which the FT Index is based.
> We are searching ways to :
> (1) limit CPU took by MSSEARCH
> (2) allow FT computation only during a BATCH period not involving User
> Activity and Perf degradation.
> Many Thanks
>
>

Full bakup of Data

A full DB backup of one of my database takes around 3 GB. Half of this
is index. All the indexes are in different filegroup. I am wondering
if I can only backup the data. For Index I can always run the script
to regenerate it.

By doing this I can reduce the size of the backup file.

Thanks
~Shijushiju (shiju.samuel@.gmail.com) writes:

Quote:

Originally Posted by

A full DB backup of one of my database takes around 3 GB. Half of this
is index. All the indexes are in different filegroup. I am wondering
if I can only backup the data. For Index I can always run the script
to regenerate it.
>
By doing this I can reduce the size of the backup file.

You can indeed backup an individual filergroup. In SQL 2000, I don't
think this is much help, because in case of a disaster you cannot get
database online by only restoring the backup of the data filegroup.

This is possible in SQL 2005, so possibly you could recover the database,
drop all indexes, and recreate them from scripts.

But before you settle on this solution, make a test to see that it really
works. I would not be surprised if you are told that you cannot drop
indexes, because they are not online. You may also find that you will also
have to drop foriegn keys to be able to drop primary keys.

And you have to ask yourself: if the database goes capoot while you are
in the midst of something else, and users are yelling that they need the
database back pronto, do you really want to be entangled in a complex
restore operation?

A databasee of 3GB is not a very big database, and neither is a backup of
it. Restoring a 3GB database in a single operation is a breeze. I would
definitely not consider a 50% reduction of the backup size to be
worth the extra pain in a stressful disaster situation.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx