October 14, 2013 at 10:00 am
I have two tables:
T1 and T2.
T1 has 1 row as
name and age
T2 has 2 rows as
name, money1
name, money2
I use left outer join and get two rows in the resulting table.
As
name, age, money1
name, age, money2
Is there any way using which i can get data like:
name, age, money1, age, money2
in one row?
October 14, 2013 at 3:29 pm
You might want to look into PIVOT (or CrossTab, as referenced in the related link in my signature).
October 15, 2013 at 4:13 am
The problem with cross tab or pivot method is that we have to hard-code total number of columns.
Here in the table t2 there may be any number of rows for a given name.
How do I handle that?
October 15, 2013 at 8:45 am
You can still cross tab or pivot, but you will need to use dynamic SQL.
October 15, 2013 at 9:46 am
ankit.gupta1 (10/15/2013)
The problem with cross tab or pivot method is that we have to hard-code total number of columns.Here in the table t2 there may be any number of rows for a given name.
How do I handle that?
Even though I prefer to do stuff like that in the application layer, I'd use the DynamicCrossTab approach as referenced in my signature, if needed.
November 27, 2013 at 5:35 pm
ankit.gupta1 (10/14/2013)
I have two tables:T1 and T2.
T1 has 1 row as
name and age
T2 has 2 rows as
name, money1
name, money2
I use left outer join and get two rows in the resulting table.
As
name, age, money1
name, age, money2
Is there any way using which i can get data like:
name, age, money1, age, money2
in one row?
I have two questions:
1. Why do you need to display 2 columns with age when they come from 1 row of T1? Wouldn't displaying it once be enough?
2. Are you updating age daily in your table?
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply