I have a stored procedure that currently brings back one row per policy number. A new table has been introduced that needs to be joined to that stored procedure. That table currently has six entries per policy but that can increase or decrease. This is sort of what I am looking at.

Although it is much more complex I think this will illustrate the issue:


Lets say this is the current stored procedure:

select * from #Policies p where policyno = 1

I need to join #NewTable to it:

select p.policyno,t.Newdata,t.akey from #Policies p
join #NewTable t on t.policyno = p.policyno
where p.policyno = 1

But I need the output to look like this:

PolicyNo NewData akey NewData akey NewData akey NewData akey

1 aaaa 1 bbbb 2 cccc 3 dddd 4

Any ideas assuming at this point I can't change the table structure. If the stored procdure always brought back one row I could flatten #NewTable first and join to that. The real issue is the stored procedure could bring back many policies and each one needs to be one row per policy with the #NewTable data flattened out per policy row.

Added:

#NewTable is dynamic so the number of entries is not fixed.

This kind of issue has come up several times in the past. Is there a maximum number of entries?

Is this for a report so that you could just concat them in a single field or do you need individual fields for each?

Simi

Is this a place where you could use Pivot?

What I ended up doing just for expediency’s sake is:

In the select:


The join:



I had left out part of the requirements. Each column name from the #NewTable had to have the column name in the select. That is becuase it needs to be exposed to Crystal reports.

I didn't check into cross tabs or pivot.


Thanks to those that replied.