Showing posts with label catalogs. Show all posts
Showing posts with label catalogs. Show all posts

Friday, March 23, 2012

How to determine frequency of

I'm new to full text catalogs and we have a vendor who's code utilizes them. The database server is SQL 2005 and I am noticing the following message in the SQL log every minute.

Changing the status to MERGE for full-text catalog "ResearchCatalog" (5) in database "DBA_Test" (11). This is an informational message only. No user action is required.

A SQL job is running the following command every minute.

exec sp_fulltext_catalog 'ResearchCatalog', 'start_incremental'

What is the typical frequency for running an incremental?

Can the messages be suppressed?

Thanks, Davestart_incremental is not a call for a timed indexing of the catalog. It simply starts an incremental population for fulltext_catalog_name based on the last time stamp of the last index to the current time of running the start_incremental. It takes the last timestamped index (there must be a column in the table that has a timestamp) and then indexes everything betwee the two times. It is different from a full index as it only updates that which it is missing instead of the entire table.

There must be something calling the procedure, whether it is a job or some kind of trigger within the software that causes it. You'll have to contact the software vendor to find out more information.

Hope that helps.|||The command is being run every minute by a SQL job. I assumed an incremental would be run perhaps once or twice a day and not every minute. What advantage is there to run this once a minute and is it possible to suppress the message seen in the log?

Dave|||I don't believe there is a way to supress it and you may not want to in case the index fails and the software vendor needs the information the log may provide to them. AFAIK, there is no way to supress indexing logs.

At a previous job, I know that Arcserve's database engine queries and writes every minute and their tech support was adamant about keeping those going. It will just depend on your vendor. I could see the advantage in updating the indexes incrementally if there is a large amount of data being written by the minute, such as in backups. Every file would be cataloged so that you could recall it easily from the backup engine and restore the file quickly. I suppose it depends on the software, but I would suggest contacting the software vendor for that information. There could be a wide range of reasons and I am only speculating based on prior experience.

Wednesday, March 7, 2012

how to delete reference to fulltext catalog

Looks like I made a mistake I hope someone can help me with. I backed
up a SQL database that implements fulltext catalogs. I thought these
would be included in the backup...I was wrong. Not a problem to
recreate the catalogs except that the database still shows the
references to the old ones. It gives me an error if I try to delete. I
get an error if I try to rebuild. I have also tried command line with
no luck:
use dev_i3
EXEC sp_fulltext_catalog 'fcAttachment', 'drop'
I appear to be stuck because I have catalog references to catalogs that
do not exist on the new server. There must be a way to manually remove
this reference and start over...I hope!
Thanks in advance.
I hope you have found a solution but if not here's my 2 cents...
First, you'll want to double-check that full-text is enabled on the database
in the new server. (see sp_fulltext_database in BOL) If not, do so and try
once more to start a rebuild on the catalogs. If this doesn't work, you'll
need to manually delete the catalogs from the sysfulltextcatalogs table and
recreate the full-text catalogs (see sp_fulltext_catalog). This should get
your catalogs back online.
Thankfully, in SQL Server 2005, the FT catalogs will be backed up and
restored as part of the database.