im pretty new to SQL and i'm just reading up on full-text searches... i need to do a a full-text search on one table i have in the database.. however I'm reading about full-text indexing/searching and a lot of pages are saying that it uses a lot of resources when searching.. i was wondering how bad is it really? we have about ~100 users who would access the database, probably the peak would be 75 at a time.. would people using a full-text searching slow it down a lot? the servr is a dell poweredge 1750 server, dual 2.8ghz xeon, 1 gig ram.. and also, about the incermental population, if i read right, it populates the catalog each time a item in the table is deleted/inserted/modified.. so would that use a lot of resources as well?
i'm just trying to see if it's worth it to enable full-text indexing for searches on the database if it doesn't slow down the server too much... or are there any better/easier ways to perform searches?
thanksIf the Text is of DataType "Char", then indexing may help u. But Indexing on VarChar Data usually does'nt help.|||The efficiency depends more upon the length and cardinality of the strings than on whether they are stored as CHAR or VARCHAR.|||Full text search is not limited to just CHAR and VARCHAR, and its strength is most appreciated when dealing with TEXT and IMAGE fields.
Check the following and drill down:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_cs_5tid.asp|||hi chauzer! we have the same scenario. we develop applications for government use and with the same concern as you do, server response is great. no slow or downtime that we experienced so far. blindman is right 'bout his statement. just want to share the experience...that's all|||thanks for the replies guys, just got it set up and see no slowdown at all and works great, thanks
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment