In general i would say instead of using a single we could accomplish the same in following steps:   1. Take dump of Table A using proc sql into SAS dataset. 2. Do the same for Table B   Load the Table B onto a proc format and apply that to table A.   This should optimize the code.   Most often the slowness of a query would depends on the connection driver either ODBC/Oracle and so on.  So the throught process should ideally be to use a method to take a dump and use the other to optimize results, so i would say use the SQL code to pull the data and not join and use SAS formatting to join the data. if it helps create use proc ds2 for parallel record processing. ... View more

Thanks team much need confirmation as well, since i tried using Spanrows and every possible permutation and combination in the SAS book for this confirmation , let me justify the same to my business. ... View more

yes that would only add it as a new column but i would like for it be as a lable for the entire table  a1This is a test Column 1 Column 2   b 2   c 3   not as above but as    a1  Column 1 Column 2 This is a test b 2   c 3   a merged single column for the entire table description more like a book mark for the table hanging out ... View more

yes thats it . so normally if i give a proc report say   proc report data=have; column ('This is a test' col1 col2); define col1 / display 'Column 1' center style(column)=[vjust=m just=l]; define col2 / display 'Column 2' center style(column)=[vjust=m just=l]; run;   would give me the outcome like  This is a test Col 1 Col 2 a 1 b 2 c  3   i would need the "This is a Test line" to span across rows and not across columns. Please advice  Thanks for the help in advance!! ... View more