IIS Index Server - Design decision

This is Interesting: Free IT Magazines  
Home > Archive > IIS Index Server > February 2004 > Design decision





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Design decision
Caroline K

2004-02-23, 3:35 am

New to indexing service .
Setup:
Win 2003 server running .Net web application and SQL
Server 2000.

Wish:
To search for words in a folder of word documents - there
are about 2000 and they will increase about 2 per day.

Thoughts:
Either use Indexing service to catalog documents in
folder and search using the OLEDB provider from SQL.
Or if we are going to do that why not populate an image
field in SQL server and full text catalog that.

I am concerned about the resources that indexing service
grabs and how quickly changes in the directory are
reflected in the catalog and user searches.
Suggestions much appreciated

Jeff Cochran

2004-02-23, 8:34 am

On Mon, 23 Feb 2004 08:56:39 -0800, "Caroline K"
<anonymous@discussions.microsoft.com> wrote:

>New to indexing service .
>Setup:
>Win 2003 server running .Net web application and SQL
>Server 2000.
>
>Wish:
>To search for words in a folder of word documents - there
>are about 2000 and they will increase about 2 per day.
>
>Thoughts:
>Either use Indexing service to catalog documents in
>folder and search using the OLEDB provider from SQL.
>Or if we are going to do that why not populate an image
>field in SQL server and full text catalog that.
>
>I am concerned about the resources that indexing service
>grabs and how quickly changes in the directory are
>reflected in the catalog and user searches.
>Suggestions much appreciated


Indexing Services uses less resources than SQL, and indexes
immediately. Depending on your documents, SQL may balk at you other
option.

Jeff
Hilary Cotter

2004-02-24, 12:35 am

What Jeff says about resources is true, however I think you will find
searching speed better using SQL FTS as using the ole-db provider via a
linked server in SQL Server is slow.

SQL Server can index word documents within a minute if you use Change
Tracking with Update index in background.


"Jeff Cochran" <jcochran.nospam@naplesgov.com> wrote in message
news:40497383.1040679538@msnews.microsoft.com...
> On Mon, 23 Feb 2004 08:56:39 -0800, "Caroline K"
> <anonymous@discussions.microsoft.com> wrote:
>
>
> Indexing Services uses less resources than SQL, and indexes
> immediately. Depending on your documents, SQL may balk at you other
> option.
>
> Jeff



Caroline K

2004-02-26, 7:34 am

Thank you both for your replies - it has been really helpful in making a decision.
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com