Re: SQL database challenge

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Lauren (anonymous_at_discussions.microsoft.com)
Date: 05/06/04


Date: Thu, 6 May 2004 04:56:02 -0700

Thanks so much! Actually, I have heard about Full-Text
Indexing but I haven't researched it yes. As a matter of
fact, we are going to want to store some additional
information along with the resume such as follow up info,
etc. I will definitely check it out.

Thanks again for your help.
Lauren
>-----Original Message-----
>Yes, it's possible. SQL Server has a feature
called "Full-Text Indexing"
>which would make this quite easy. However, I don't know
that I'd use SQL
>Server for this task, unless you'll be storing other data
along with the
>resume (e.g. the various fields from the resume actually
typed in to a
>normalized data structure, current job status, etc). If
you only want to
>have a searchable resume repository, it may be simpler to
convert the
>resumes to MS Word, text files, or PDF format and use
Microsoft Indexing
>Service instead. I don't think this task should be
difficult to accomplish
>with either of these products.
>
>
>"Lauren" <lmaurer@dorland.com> wrote in message
>news:8d1f01c432b8$9634a3e0$a001280a@phx.gbl...
>> Hi all,
>>
>> I am very new to using the SQL language and SQL Server
>> 2000 so I am curious about the possiblity of a project I
>> have been assigned to within my office environment.
>>
>> I need to create a resume database that would allow for
a
>> user to pull up specific resumes based on keywords or
>> text that is entered in some kind of search field. For
>> example, if a user opens this database and types
>> in "SQL", I would like the database to return some kind
>> of form with a list of all the peoples' names that have
>> that word somewhere in their resumes. Then it would be
>> great if the user could click on a name and pull up that
>> specific person's resume. Is this possible?
>>
>> I was thinking that maybe we can scan the resumes into
>> some kind of scanner and then use an OCR to translate
the
>> scan into text (something like this is already in
Windows
>> XP, which I have. Basically, I can scan hard copy into a
>> digital sender which saves a Tiff file, and then I run
>> Document Imaging on the Tiff file) and maybe that text
>> could be stored into and be retrieved from one of our
>> servers. I just don't know what to do with the
>> information after that.
>>
>> By the way, I am using Windows XP, Office XP and Office
>> 2003. If anyone has any idea on how to accomplish this
>> (if it's possible) or can give me an idea of where I can
>> find this info, I would greatly appreciate it.
>>
>> Thanks!
>> Lauren
>
>
>.
>



Relevant Pages

  • Re: SQL database challenge
    ... SQL Server has a feature called "Full-Text Indexing" ... > digital sender which saves a Tiff file, ... > By the way, I am using Windows XP, Office XP and Office ...
    (microsoft.public.sqlserver.datamining)
  • Re: New indexing algorithm??
    ... I took a look at a couple of the CopperEye whitepapers, ... SQL Server clustered index is optimized for range retrievals at ... SQL Server's indexing flexibility, once index keys are decided, is ...
    (microsoft.public.sqlserver.server)
  • Re: accent insensitive search (any definitve solution?)
    ... Text Search with SQL Server 2000 and the indexing services. ... This is the installation program we will use to ... You will then have to create a schedule for the indexation process. ...
    (microsoft.public.inetserver.indexserver)
  • Re: LIKE, CONTAINS and Full Text Indexing
    ... "michael" wrote in message ... predicate in the RowFilter of a DataView. ... should I explore Full Text Indexing and using a CONTAINS ... Would it be best to execute this on the SQL Server rather than ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Full Text Indexing Option Disabled
    ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ... feature because of the bug in SQL Server Enterprise Manager that disables ... It implies that because the account is ...
    (microsoft.public.sqlserver.fulltext)