June 15, 2004 at 8:49 am
Are there any known problems or caveats with running the Indexing Service on a SQL 2000 Server? We have some servers with Windows 2003, but most are still running Windows 2000.
Thanks!
Ben Reeder
Deere and Company SQL Server DBA
June 18, 2004 at 8:00 am
This was removed by the editor as SPAM
July 2, 2004 at 12:32 am
Is it possible to run the indexing service on a different server and point SQL to it???
July 2, 2004 at 8:53 am
Yes. I figured out that you can do it that way too.
July 2, 2004 at 10:00 am
I had one problem 2 times with Hard Drive and 1 problem with CPU on the machine that runs SQL Server 7 and IIS with Indexing Service to let report users browse their files better. This server has lots of memory and about 3 GB of a free disk space on a particular drive. All of sudden we are getting messages "Disk Space Is low" it happens when indexing service is indexing those files or whatever. The space is free again after like 10 min. The third time we had CPU higher then normal. The person who mantained the application on this server did a research and told me it could be expected. I am attaching 2 extracts from my records. Please, make sure you have enough drice space and CPU where you run CI Service.
.................I just get a message from <servername> that E drive is nearly full and only 142 MB is free. The most space was used by INETPUB directory 2.51 GB CI service creates some index files. ..... We previously had some trouble with CI Service rebuilding the indexes in terms of requesting a lot of space on the hard drive for temp data during index rebuild.................
....................I was checking <servername>.....today and found that CPU utilization was higher then normal. It is about 28-30%, which is high. I am absolutely sure that the previous times I checked the server it was normal at about no more then 5 % ................The process that consumes CPU is CI Service (Content Indexing Service) that is indexing something in <web documents> according to <app support name>
Regards,Yelena Varsha
May 16, 2005 at 10:15 am
I am very interested in how did you configure the SQL's linked server to point to a different machine's indexing service. I have tried but it doesn't seem to be able to link to a different machine's indexing service. It keeps giving me an error "There is no catalog" while I am sure the index service on the other machine is set up and running properly. When I set up the same index service catalog locally on the SQL server machine, everything works fine. Have I set anything wrong or there are other tricks I missed.
My configurations are as following:
1. Linked Server: [the second server name] (the 2 machines are in the same domain)
2. Data source Provider name: Microsoft OLE DB Provider for Indexing Service
3. Product name: Test Index Server
4. Data sources: Web
5. Location: [blank]
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply