Table Joins or Linq/Lambda expression comparison

Question

0.00/5 (No votes)

See more:

I have six tables in my SQL Server database.

Step 1: I UNION ALL Table 1, Table 2 and Table 3 into Datatable1.

Step 2: I UNION ALL Table 4, Table 5 and Table 6 into Datatable2.

In all the 6 tables the common columns are AlbumID,PictureID,StoryID.

Now I want to compare these columns in both the Datatables and put a flag (True) in Datatable1 where the data in both the datatables match else False.

I am thinking to use Linq or Lambda Expression to do the comparison. Is this the correct/best way to do this? OR should I go for TABLE JOINS?

Basically the table should have 4 columns :-

AlbumID, PictureID, StoryID, Flag
Flag would be true only if AlbumID or PictureID or StoryID is present in Datatable2

Posted 6-Jan-13 5:05am

Member 7781963

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2013-01-06T05:39:00

I guess it's a matter of opinion, but personally I would either join the tables or use an EXISTS[^] clause.

However, the first thing I would do is to stop to think the database design itself. If you have tables that have so many common columns, it raises the question if the database s normalized properly.

So without knowing anything more about the tables, I would advice you to have a closer look at the database design and consider if instead of having 6 tables which all have columns AlbumID,PictureID,StoryID could you simplify the design.