Right,

Sorry for my previous brief posts with bad spelling and grammer. Here is what I have found:

The optimiser deals better with a sub query look up rather than a looking...

the clustered index is already there on ndate as it is a date sequence table.....

the issue is with the high volume policy table... however i'm am just experiment with using...

You can select the distinct values of customerid and noteid, then pass these to a scalar function which queries the underly table something like this:

create function gc

@customerid varchar(50

@noteID varchar(50)

as

declare @ss...