Tuesday, November 6, 2007

Website Search engine component research

Goal here is to obtain a component in asp or .net (any) that allows us to save the indexing into SQL Server 2005.

Here are the goals:
-SQL Server 2005
-.NET or ASP
-Can schedule updates to the index
-Needs to be on a Windows 2000 or Windows 2003 server
-Will have to run once a week.
-We can choose a directory for file scans. This is not an entire site scan.

Keyoti
http://www.componentsource.com/products/keyoti-search-pro-asp-net/index.html
Price: 391.02 Single Developer license
Does not say where the indexing is stored, but references a directory.
-SQL Server 2005 - NA
-.NET or ASP - .NET
-Can schedule updates to the index
-Needs to be on a Windows 2000 or Windows 2003 server - fine
-Will have to run once a week.
-We can choose a directory for file scans. This is not an entire site scan.

OraDeveloper tools: Doesn't integrate with SQL Server, looks like it focuses on Oracle

FindinSite-MS - .NET - V1.51 : Looks like it places all in a directory

Summary: After spending an hour looking for components, it looks like we are going to use search engine builder professional. This will allow us to put our search information into an Access database. We are then going to migrate the data from there into SQL Server. It appears as though most of these search engine components are building text indexes in a directory. My assumption is that they can work on sites and on distributable disks as this seems to be a common high note on the sales pitches.

No comments: