Estimate time to populate full text index

Can someone give me an estimate time to populate a full-
text index, SQL Server 2000:
-14 million rows,
- each row is about 1 paragraph long. (approx 400 words and is stored in a LONG TEXT field)
- Language of the text: mixed.
- W.H.:a single CPU 2.8GHZ with 2GB Ram and have 300GB disk space
-incremental.
it has been running for 3 days now and who knows where we are...
Any way to speed up..
Thanks
mustafa,
Given your hardware configuration, and a table with 14 million rows will
take a substitational amount of time, approx 5 to 8 days.
Your best bet is to attempt to stop the Full or Incremental population and
consider horzatioanlly partitioning the table into several smaller tables,
perhaps broken up by date or PK range. If you plan to continue this, I'd
highly recommend that you consider upgrading all aspects of your hardware.
Specifically, consider a multiple CPU server with 2 or more GB of RAM with
your FT Catalogs on a separate disk controller and disk array configured as
RAID0 or RAID10. You should also set the resource_usage level of the
MSSearch service to 5 via sp_fulltext_service 'resource_usage', 5. However,
this will not help you now. I'd also recommend that you review the SQL
Server 2000 BOL title "Full-text Search Recommendations" and the following
FT Deployment white paper: INF: SQL Server 2000 Full-Text Search Deployment
White Paper at:
http://support.microsoft.com/default...b;en-us;323739
Regards,
John
"mustafa jarrar" <anonymous@.discussions.microsoft.com> wrote in message
news:6EC893FD-DD03-4FA1-BE01-052A19EB03AB@.microsoft.com...
> Can someone give me an estimate time to populate a full-
> text index, SQL Server 2000:
> -14 million rows,
> - each row is about 1 paragraph long. (approx 400 words and is stored in a
LONG TEXT field)
> - Language of the text: mixed.
> - W.H.:a single CPU 2.8GHZ with 2GB Ram and have 300GB disk space
> -incremental.
> it has been running for 3 days now and who knows where we are...
> Any way to speed up..
> Thanks
>

estimate on how long it might take to full-text index a table with 21,000 rows?

i need to full-text index a table so that i can easily search the text fields of that table.. the table has about 21,000 rows, and i was wondering how long it might take to full-text index it?
thanksBetween four seconds and three years, depending on hardware configuration, table contents, and server load.

On a (very slightly) more serious note, I don't know of any way to give you a meaningful estimate.

-PatP

Error: SQL server failed to communicate with Full-Text Service

Hello,

I've enabled full-text indexing on one of my tables, and the following query used to work:

SELECT *
FROM TempAttachment
WHERE CONTAINS(attachment, 'text')

However, now I get the following error:

Msg 9955, Level 16, State 1, Line 1SQL server failed to communicate with Full-Text Service (msftesql). The system administrator must make sure that same service account is used for both services and the service account has the permission to auto start the full-text service.

I've checked the configuration and verified that both accounts are the same. I've restarted the services, and tried rebooting, and still no luck. I did a search on this error, and found this page from MSDN, which doesn't help me much: http://msdn2.microsoft.com/en-us/library/aa337365.aspx.

Has anybody come across this before? Any help would be greatly appreciated!

Just want to be sure, which 2 services' account did you update?

|||

Thanks for your reply.

I didn't update any settings. I went to SQL Server Configuration Manager and selected "SQL Server 2005 Services" on the left menu. On the right side, I right-clicked and viewed properties of "SQL Server FullText Search" and "SQL Server". They both have the same log-on account (Local System).

This morning, I tried to back up my database and got a clue about this issue when the back up failed. It says "The backup of full-text catalog is not permitted because it is not online. Check errorlog file for the reason that full-text catalog became offline and bring it online..." I searched the error logs for my table name and didn't find anything (other than the backup failing because of it). Any ideas? Thanks.

|||

Okay, I found the problem!

Somehow, I didn't have permissions to the directory where the full-text data was being stored. (I'm unclear on how this happened - maybe someone else can reply if they have an idea?)

First, run the following query to find the path to your full-text catalog:

SELECT * FROM sysfulltextcatalogs

Then check the permissions for the directory or directories identified.