Full text search and replace

Need to search through a database and remove references to a company from
it. Grrr!
How can I do this? Do I need to write a client script to load each offending
record, or can I do it with SQL?
Conceptually I want to do
REPLACE IN Resumes TEXT 'Company Name' WITH ''
This is a full text table.
whats the best approach?
I'd try something like this:
declare @.replacement varchar(200)
set @.replacement='test'
update testtext
set textcol=
substring(textcol,1, patindex('%company%',textcol)-1)
+@.replacement +
substring(textcol,patindex('%company%',textcol)+le n('company'),datalength(te
xtcol)-patindex('%company%',textcol)+len('company'))
from testtext
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Andy Gilman" <andygilman2@.hotmail.com> wrote in message
news:utvmJQubEHA.904@.TK2MSFTNGP09.phx.gbl...
> Need to search through a database and remove references to a company from
> it. Grrr!
> How can I do this? Do I need to write a client script to load each
offending
> record, or can I do it with SQL?
> Conceptually I want to do
> REPLACE IN Resumes TEXT 'Company Name' WITH ''
> This is a full text table.
> whats the best approach?
>

FTS Index Size

Are there any references that help with estimating the size of a FTS index, or the whole catalog? I'm trying to do some capacity planning, and can't find anything to help me guess how much disk I'll need.
Unfornitually I haven't seen anything out there on how to do capacity planning for FTS.|||This is surprising to hear, as I thought FTS was a first-class, well-supported feature.
|||

MikeBlaszczak wrote:

This is surprising to hear, as I thought FTS was a first-class, well-supported feature.

Hi Mike,
Nope, it hasn't been a first-class index in the same perspective as clustred or non-clustred index. However, that will change with the next release of SQL Server 2008, codename Katmai. I've long ago advocated this while a FTE, but alas it has taken many years to occur.

Regards,
John

John T. Kane
Search Evangelist, Intellisearch
email: john.kane@.intellisearch.no

|||Hi, John.

I'm not worried about it being a first-class index. I'm worried about it being a first-class feature. That is: something that's well-supported and usable in enterprise applications. If there's no documentation about how to do capacity planning for a deployment, it's hard for me to think that FTS is a first-class feature.

FTS Index Size

Are there any references that help with estimating the size of a FTS index, or the whole catalog? I'm trying to do some capacity planning, and can't find anything to help me guess how much disk I'll need.
Unfornitually I haven't seen anything out there on how to do capacity planning for FTS.|||This is surprising to hear, as I thought FTS was a first-class, well-supported feature.
|||

MikeBlaszczak wrote:

This is surprising to hear, as I thought FTS was a first-class, well-supported feature.

Hi Mike,
Nope, it hasn't been a first-class index in the same perspective as clustred or non-clustred index. However, that will change with the next release of SQL Server 2008, codename Katmai. I've long ago advocated this while a FTE, but alas it has taken many years to occur.

Regards,
John

John T. Kane
Search Evangelist, Intellisearch
email: john.kane@.intellisearch.no

|||Hi, John.

I'm not worried about it being a first-class index. I'm worried about it being a first-class feature. That is: something that's well-supported and usable in enterprise applications. If there's no documentation about how to do capacity planning for a deployment, it's hard for me to think that FTS is a first-class feature.