Post reply

Sql Design help

  • May 24, 2007 at 7:54 am

    #178840

    iam running a website ,its a jobsite

    with only 200mb of sqlserver space,

    no entripise manager connection allowed, only a web based interface just to create tables,drop,edit and to run sql queries

    iam using that space to store job postings.

    iam doing a search on ntext field which is jobdescription

    where jobdescription like '%vb.net,asp.net%'

    that sql query execution takes time

    iam planning to make another dummy table, where job postings will be done, then i will extract data from that particular table to mainjobpostings table on a particular time

    iam planing to index jobdescription field, which is ntext

    is it the proper idea to do so, how can i speed up the sql queries which are for job search ?

    any ideas and help will be appreciated, iam confused about speeding up sql queries

    can i index jobdescription field ? for speed

    <a href="http://www.websolsoftware.com"> For IT jobs click here</a>

    *Sukhoi*[font="Arial Narrow"][/font]

  • May 27, 2007 at 11:51 pm

    #709158

    You should not search in ntext field.

    It's not a SQL Server job.

    You should split Job Descriptions into parts you are interested in when you are saving it. And save every part separately, in it's own row. Those rows, of course, should be joint by some "JobID".

    Then fast searching should not be a problem.

    _____________
    Code for TallyGenerator

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply