How can I combine SQL select by columns?

I would like to combine results from a number of tables/queries to produce the table shown in ResultsD.
Please note I am limited to SQL server 2000.
The tables are not related and the fields in the rows in the output ResultsD are therefore not related to each other.




1                Apple        1.0
2                Pear          3.0            
3                Lemon      5.0
4                Null           6.0
Null           Null           7.0
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
In SQL Server 2000 you can't. Being a relational database you need to find something that can relate those 3 tables.
In newer versions of SQL Server it's possible to attribute row numbers to the records and use it for relating data. In this case you can't do what you want.
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Can you explain why you want this?  Perhaps there is an easier workaround.

>Please note I am limited to SQL server 2000.
Okay, but be advised that you're running six versions old (2005 > 2008 > R2 > 2012 > 2014), which means Microsoft support is over, experienced experts are unlikely to maintain skillsets exclusively to 2000, and in the event of any server/database crash the odds of not being able to restore back to 2000 diminish greatly.  I'd tell your employer to spend some money to protect their data and upgrade.
Scott PletcherSenior DBACommented:
You must use temp tables in SQL 2000; might be best anyway, given the joins you need to do.

--Setup: we must add an identity to each result to join on---------------------------------
SELECT IDENTITY(int, 1, 1) AS ident, *
INTO #ResultsA
FROM ResultsA a
ORDER BY a.col1

SELECT IDENTITY(int, 1, 1) AS ident, *
INTO #ResultsB
FROM ResultsB b
ORDER BY b.col1

SELECT IDENTITY(int, 1, 1) AS ident, *
INTO #ResultsC
FROM ResultsC c
ORDER BY c.col1

--Ok, now we're ready for the final join itself-------------------------------------------------------
SELECT a.col1, b.col1, c.col1
FROM #ResultsA a
    b.ident = a.ident
    c.ident IN (a.ident, b.ident)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

dgloverukAuthor Commented:
Thank you Scott, to answer Jim, my reason for asking is as follows.  I have a view of results.... For arguments sake lets say customer orders.  There are several things from this list of results that i need distinct lists of e.g salespersons, item categories and payment types to build filters in the user interface with options only relating to the orders being retrieved.  I cannot requery the view for distinct values of each column of interest since the underlying view is rapidly evolving and the view is fairly process intensive anyway to be doing a series of distinct selects on each column.  What i was going to try was querying the view for each of the columns of interest and their distinct values and return them as one table for building filter options from in the user interface.  I thought the approach above would allow me to return a complete set of filters options for several fields at once without having to action a series of queries from the client to generate each filter option.
Vitor MontalvãoMSSQL Senior EngineerCommented:
What i was going to try was querying the view for each of the columns of interest and their distinct values and return them as one table for building filter options from in the user interface.
Ok, but can't you add to your query a field that can be related to all these records so it can used for a JOIN?
dgloverukAuthor Commented:
I think what I'm going to do is put the original Query results into a temporary table and then return the distinct selections from this temporary table to get the filter options as well as the temporary table itself.
Originally I didn't go in this direction because I did not want to break up the process of capturing the query results and then getting then querying for filter options since they could have changed and to get the distinct options based on the original query would have been further overhead for each filter.  But what I didn't know which I've read is that you can return multiple sets of data from a single execution of a stored procedure using NextResult and this basically solves my problem of getting the query and a list of filters based on that query, without resubmitting the original query.
Does this sound like a reasonable approach?
Vitor MontalvãoMSSQL Senior EngineerCommented:
The NextResult is a .NET method, right?
We are giving you only native SQL Server solutions. Can't talk about the NextResult since isn't my expertise area.
dgloverukAuthor Commented:
That's right.
I'm assuming that internally to SQL server a stored procedure can return multiple sets of results for handling?
If so, I wasn't aware of this else I might have guessed earlier that there would be a method with .NET to cycle through the different sets of results.
Vitor MontalvãoMSSQL Senior EngineerCommented:
The only way a stored procedure has to return values is using OUTPUT parameters. You can read more about it here.
dgloverukAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 500 points for ScottPletcher's comment #a40468061
Assisted answer: 0 points for dgloveruk's comment #a40468836

for the following reason:

Thank you for your help guys!
Scott PletcherSenior DBACommented:
>> I'm assuming that internally to SQL server a stored procedure can return multiple sets of results for handling? <<

That is correct.  By default SQL will return the first result set to the caller, but there are methods to get any additional result set(s), if any.

You can also return a single integer return code, using
RETURN <int_value>
By default, SQL will return 0.

Finally, as noted by Vitor, you can return one or more scalar (single-value) parameters by specifying them as "OUTPUT" parameters.
Scott PletcherSenior DBACommented:
I've done the same thing before.  You have distinct lists but you want to see them in a compact format.  Joining by line# works perfectly in those cases.
dgloverukAuthor Commented:
Thanks guys!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.