URL Parameters work too

http(s)://MyDomain.com/ReportServer/ReportPath/Report?

&rs:Format=EXCEL&rcmitFormulas=true

http://ezinearticles.com/?URL-Parameters-Used-in-Reporting-Services&id=176858

ah....makes sense, will give it a shot

no index on this field (why would you put on comments field?)

4.2M records in table

So the answer is...

1.) I'm trying to run this locally and getting an error related to the amount of memory

2.) When deployed to the server I get an error: Product...

spam on the front page?

Sergiy,

There are no leading spaces in the field I just put that in out of habbit. The query you mention is what I used originally and I am getting an...

You can also simplify this...

Declare @NAMEX varchar(100)

Set @NAMEX = 'S'

SELECT * FROM testTbl WHERE NAMEX Like @NAMEX + '%' ORDER BY NAMEX

cheers

Not sure how to fix the like expression but you can do it like this:

/*** CODE ***/

create table temp (accn varchar(25))

insert into temp (accn) values ('123123123123123123')

insert into temp (accn) values...

Thanks Lynn,

I started out using 'like' but had the same result.

Ugh...I really hate when business process folks decide how data should be stored in the application w/o consulting any...

I would use integration services...

What does the table structure look like? Do you have a query that already returns this data for your report?

Nice...so at 21% of the Finding Similar Records I get an 'Unhandled exception' that indicates corrupt memory. Any ideas???

It seems to be hung on the 'Finding Similar Records' step...i'll let it run for a while and see how it goes...

That is the query in my 'Data Reader Source' that is being passed into my 'Fuzzy Grouping' then is to be inserted into a table on the same server...

This may be the issue...I'm concatenating a bunch of fields to come up w/ what would be considered a dupe...

So basically if the customer + full address + Comment is...