"SqlBeginner" <SqlBeginner@discussions.microsoft.com> wrote in message
news:9CF3678B-2D77-4510-A167-F7C5131ED4E7@microsoft.com...
> Hi All,
>
> I have created a DB design for implementing WIKI in one of my project. I
> have created a column of data type NText to store the content of the wiki
> page. Normally ppl would store the wiki pages as flat files but since my
> project work on a web farm scenario I need to save the contents within a
> DB
> (as per our company policy... lets not get deep into this :) ).
>
> Though my app is working fine. When I try to search for a document at
> frequent intervals its throwing a "timeout error". [I don't think that
> increasing the timeout minutes in the front end would solve this on a long
> term basis]. I guess its because of this large data type. FYI, as of now
> we
> have just few hundreds of rows.
>
> Any pointers on how to avoid this error would be really helpful to me.
>
> Regards
> Pradeep

"SqlBeginner" <SqlBeginner@discussions.microsoft.com> wrote in message
news:9CF3678B-2D77-4510-A167-F7C5131ED4E7@microsoft.com...
> Hi All,
>
> I have created a DB design for implementing WIKI in one of my project. I
> have created a column of data type NText to store the content of the wiki
> page. Normally ppl would store the wiki pages as flat files but since my
> project work on a web farm scenario I need to save the contents within a
> DB
> (as per our company policy... lets not get deep into this :) ).
>
> Though my app is working fine. When I try to search for a document at
> frequent intervals its throwing a "timeout error". [I don't think that
> increasing the timeout minutes in the front end would solve this on a long
> term basis]. I guess its because of this large data type. FYI, as of now
> we
> have just few hundreds of rows.
>
> Any pointers on how to avoid this error would be really helpful to me.
>
> Regards
> Pradeep

"SqlBeginner" <SqlBeginner@discussions.microsoft.com> wrote in message
news:FC6EAA48-77B9-4CE3-B1AC-E603B7D8C38B@microsoft.com...
> Sorry for responding late. Can you educate me on how to enable or make use
> of
> Full text search in sql server 2000?
>
> Any pointers regarding this would be really helpful.
>
> Regards
> Pradeep
>
> "Uri Dimant" wrote:
>
>> Hi
>> Have you considered using Full-Text Catalog for searching ?
>>
>>
>> "SqlBeginner" <SqlBeginner@discussions.microsoft.com> wrote in message
>> news:9CF3678B-2D77-4510-A167-F7C5131ED4E7@microsoft.com...
>> > Hi All,
>> >
>> > I have created a DB design for implementing WIKI in one of my project.
>> > I
>> > have created a column of data type NText to store the content of the
>> > wiki
>> > page. Normally ppl would store the wiki pages as flat files but since
>> > my
>> > project work on a web farm scenario I need to save the contents within
>> > a
>> > DB
>> > (as per our company policy... lets not get deep into this :) ).
>> >
>> > Though my app is working fine. When I try to search for a document at
>> > frequent intervals its throwing a "timeout error". [I don't think that
>> > increasing the timeout minutes in the front end would solve this on a
>> > long
>> > term basis]. I guess its because of this large data type. FYI, as of
>> > now
>> > we
>> > have just few hundreds of rows.
>> >
>> > Any pointers on how to avoid this error would be really helpful to me.
>> >
>> > Regards
>> > Pradeep
>>
>>
>>

"Uri Dimant" wrote:

> Hi
> Have you considered using Full-Text Catalog for searching ?
>
>
> "SqlBeginner" <SqlBeginner@discussions.microsoft.com> wrote in message
> news:9CF3678B-2D77-4510-A167-F7C5131ED4E7@microsoft.com...
> > Hi All,
> >
> > I have created a DB design for implementing WIKI in one of my project. I
> > have created a column of data type NText to store the content of the wiki
> > page. Normally ppl would store the wiki pages as flat files but since my
> > project work on a web farm scenario I need to save the contents within a
> > DB
> > (as per our company policy... lets not get deep into this :) ).
> >
> > Though my app is working fine. When I try to search for a document at
> > frequent intervals its throwing a "timeout error". [I don't think that
> > increasing the timeout minutes in the front end would solve this on a long
> > term basis]. I guess its because of this large data type. FYI, as of now
> > we
> > have just few hundreds of rows.
> >
> > Any pointers on how to avoid this error would be really helpful to me.
> >
> > Regards
> > Pradeep
>
>