Databases
StackOverflow2013
Postsdbo
POSQL Server 2005 -Join based on criteria in table column
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL Server 2005 -Join based on criteria in table column
    primarykey
    data
    text
    <p>Using SQL Server 2005, what is the most efficient way to join the two tables in the following scenario ?</p> <p>The number of records in each table could be fairly large about 200000 say.</p> <p>The only way I can currently think of doing this is with the use of cursors and some dynamic SQL for each item which will clearly be very inefficient.</p> <p>I have two tables - a <code>PERSON</code> table and a <code>SEARCHITEMS</code> table. The <code>SEARCHITEMS</code> table contains a column with some simple criteria which is to be used when matching records with the <code>PERSON</code> table. The criteria can reference any column in the <code>PERSON</code> table.</p> <p>For example given the following tables :</p> <p><code>PERSON</code> table</p> <pre><code>PERSONID FIRSTNAME LASTNAME GENDER AGE ... VARIOUS OTHER COLUMNS 1 Fred Bloggs M 16 .... 200000 Steve Smith M 18 </code></pre> <p><code>SEARCHITEMS</code> table</p> <pre><code>ITEMID DESCRIPTION SEARCHCRITERIA 1 Males GENDER = 'M' 2 Aged 16 AGE=16 3 Some Statistic {OTHERCOLUMN &gt;= SOMEVALUE AND OTHERCOLUMN &lt; SOMEVALUE} .... 200000 Males Aged 16 GENDER = 'M' AND AGE = 16 </code></pre> <p><code>RESULTS</code> table should contain something like this :</p> <pre><code>ITEMID DESCRIPTION PERSONID LASTNAME 1 Males 1 Bloggs 1 Males 200000 Smith 2 Aged 16 1 Bloggs .... 200000 Males Aged 16 1 Bloggs </code></pre> <p>It would be nice to be able to just do something like</p> <pre><code>INSERT INTO RESULTSTABLE SELECT * FROM PERSON P LEFT JOIN SEARCHITEMS SI ON (APPLY SI.SEARCHCRITERIA TO P) </code></pre> <p>But I can't see a way of making this work. Any help or ideas appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmarc_s
    1. USPaul Elliott
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSQL Server 2005 -Join based on criteria in table column
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSQL Server 2005 -Join based on criteria in table column
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSQL Server 2005 -Join based on criteria in table column
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat problem are you trying to solve exactly? Is the requirement just to join these 2 tables?
      singulars
      1. POSQL Server 2005 -Join based on criteria in table column
      1. USAli
    2. COThe requirement is to insert the results from any matching records into a results table - it doesn't necessarily need to be using a join it just needs to be efficient - I see the join ultimately being the most efficient if it could be achieved.
      singulars
      1. POSQL Server 2005 -Join based on criteria in table column
      1. USPaul Elliott
    3. COI think we should have a middle table between person and search item because the result table's size as it's currently described will explode out of proportion. I have thought about it and I couldn't come up with a better solution then using a cursor, unless you know all search criteria combinations (which I highly doubt).
      singulars
      1. POSQL Server 2005 -Join based on criteria in table column
      1. USAli
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload