Try

Select Sum((DataLength([ColumnName])-DataLength(RePlace([ColumnName],'SearchFor','')))/DataLength('SearchFor'))

   from Table

Also have a look at http://www.sqldts.com/default.aspx

-- Part II User commands

-- User supply VB / ASP with "Select * from Tmp Where Company_Name='Company ''1'''"

Set QUOTED_IDENTIFIER off -- More readable

Insert Tmp

Select "Select *...

Hopefully I am on the right track. Had a similar problem last week. Solution was to replace all the single quotes in the data with two single qoutes. Problem was...

Any peer pressure to change? I’ll stay a purist (numbers guy)

Code adapted from BOL 2000, used to work in 6.5 with the 255 limit.

DECLARE @SQLString1 VARCHAR(8000),

@SQLString2 VARCHAR(8000)

SET @SQLString1 = 'SELECT * FROM Periods...

I think mmcork covered about all the bases.

Maybe you can start with a SELECT with a WHERE clause and execute it. Then to the update with a transaction and SELECT...

Should'nt nulls be excluded entirely from the set being averaged On smaller sets it may have significant effect.

Read BOL 2000: Using RAND

Execute the following

Select f.a,Rand(f.a),rand()

   from (Select 0 union Select 1 union Select 2) as f(a)

I'll rather go with mccork's suggestion.

select SeqNum=Identity(INT,1,1),

b.idProduct,b.chrProductName,c.chrSubDeptName 

INTO #TMP from 

Agree with Andy Warren suggestion or add a column confirmed(Yes,No,Maybe,etc.).

BOL 2000: The char data type is a fixed-length data type when the NOT NULL clause is specified. If a value shorter than the length of the column is inserted...