Try this on for size:CREATE TABLE #TestHldgs (
    HoldingID float NULL,
    ClientURN float NULL,
    IndicatorID float NULL,
    IndicatorTypeId float NULL,
    IndicatorStatusID float NULL,
    DateApplied datetime NULL
);
INSERT #TestHldgs (HoldingID,...

Take a look at this and let me know what you think:CREATE TABLE #Source (
    ID varchar(50) NOT NULL PRIMARY KEY CLUSTERED,
    nameFull varchar(50),
    salutation varchar(50),
    nameFirst varchar(50),
    nameLast varchar(50),

Gail is correct.   The problem here is that there's nothing else in the table on which you can base any form of sort on, other than the column that is...

The security context that SSRS runs under will usually (if not always) be the SSRS Service Account, so that account will need at least read access to that other database.

That's one of the difficulties of having multiple columns for the same kind of data in a given row.   If I had this I'd look to re-design it to have...