Please, check your sample data. It won't run.

Jack Corbett (11/12/2015)

---

Sean Lange (11/12/2015)

---

Brandie Tarvin (11/12/2015)

---

Sean Lange (11/12/2015)

---

djj (11/12/2015)

---

Grant Fritchey (11/12/2015)

---

Still, could be fun. Build out a nested CTE inside a function, use the same table aliases...

I'm guessing that it would be better to correct this from the start instead of adding work to a result that you already calculated.

Jason-299789 (11/12/2015)

---

The best way would be to use the CROSS TAB method, mentioned in this article : http://www.sqlservercentral.com/articles/T-SQL/63681/

Will the number of columns be limited to 3 or will it depend...

Use CROSS TABS[/url] with the MAX() function, probably with a row number to avoid losing rows.

I'm really not sure what's your expected output based on that sample data and explanation.

Use CROSS TABS[/url] with the MAX() function.

The syntax errors would be the least of your problems if you're not expected to run your code against a database. You're missing half of the logic for your queries....

yb751 (11/11/2015)

---

Well I just finished talking with our Dev team and I realized that the attributes do not need to be updated individually. Also any searches would be offloaded...

Sean Lange (11/11/2015)

---

rxm119528 (11/11/2015)

---

Apologies for the missing loop. Thanks for the different approaches. I just wanted to learn the other ways we can append those sequence of numbers with out...

I'm not sure there's something documenting either that the id is reusable nor it's completely unique. It might not be an identity either if that's what you were expecting.

You shouldn't...

I see that Sean got the simpler route by defining hard coded values.

This should allow the results to grow in an easier way if needed.

DECLARE @VARABLE VARCHAR(10) = 'AB.DEF';

WITH

E(n)...

Kristen-173977 (11/11/2015)

---

It would to me if you were OUTER JOIN'ing the KeyValue table 137 times...

You might not be able to get rid of that table completely, but with some analysis, you could create several tables once you identify common attributes to define entities correctly.

EXISTS should be better than a MERGE which might need an expensive sort operation.

How much are you deleting and how much are you keeping in the table? Maybe that would...

Probably this will return the expected rows?

Select dbo.R_ResrvStock.Vin,

R_Txt_Temp.Vinnumber,

R_Txt_Temp.Model_Code

from dbo.R_ResrvStock

inner join R_Txt_Temp on Right (RTRIM(dbo.R_ResrvStock.Vin),LEN(R_Txt_Temp.VinNumber))=R_Txt_Temp.VinNumber

Without DDL and Sample data as insert...