Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>crazy design, possibly the fake table names makes it stranger than it is.</p> <p>create indexes based on select usage.</p> <p>if you are searching on actual first names like "Joe" you need an index on FirstNames.Name</p> <p>if you are searching on first name ids like 123, you have an index: FirstNames.FirstNameId</p> <p>if you want to search on FirstNames.name and/or MiddleNames.name and/or Surnames.name you need to have indexes on the combinations that you will use, and the more you make, the harder for the query to pick the best one.</p> <p>ditch the view and write a dedicated query for the purpose:</p> <p>go after first/middle</p> <pre><code>select FirstNames.name ,MiddleNames.name ,Surnames.name FROM FirstNames INNER JOIN MiddleNames ON FirstNames.FirstNameId=MiddleNames.FirstNameId INNER JOIN Surnames ON FirstNames.FirstNameId=Surnames.FirstNameId WHERE FirstNames.Name='John' AND MiddleNames.Name='Q' </code></pre> <p>go after last</p> <pre><code>select FirstNames.name ,MiddleNames.name ,Surnames.name FROM Surnames INNER JOIN FirstNames ON Surnames.FirstNameId =FirstNames.FirstNameId INNER JOIN MiddleNames ON FirstNames.FirstNameId=MiddleNames.FirstNameId WHERE Surnames.Name='Public' </code></pre> <p>just make sure you have indexes to cover your main table in the "where" clause</p> <p>use SET SHOWPLAN_ALL ON to make sure you are using an index ("scans" are bad "seeks" are good")</p> <p><strong>EDIT</strong><br> if possible break the names apart before searching for them:</p> <pre><code>exec uspSearchForPeople 'joe',null,'blogs' (1 result) exec uspSearchForPeople 'joe',null,null (1 result) exec uspSearchForPeople null,null,'blogs' (2 results) exec uspSearchForPeople 'jon',null,'skeet' (1 result) exec uspSearchForPeople null,null,'skeet' (1 result) </code></pre> <p>within the stored procedure, have three queries:</p> <pre><code>if @GivenFirstName is not null --search from FirstNames where FirstNames.name=@value &amp; join in other tables else if @GivenMiddleName is not null --search from MiddleNames where MiddleNames.name=@value &amp; join in other tables else if @GivenLastName is not null --search from Surnames where Surnames.name=@value &amp; join in other tables else --error no names given </code></pre> <p>have an index on all three tables for Names.</p> <p>if you can not split the names apart, I think you are out of luck and you will have to table scan every row in each table.</p> <p>Just think of a phone book if you don't use the index and you are looking for a name, you will need to read the entire book</p>
    singulars
    1. This table or related slice is empty.
    1. POMost efficient design to search for this data in my database?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USracer x
    1. USracer x
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThanks for the reply. I didn't know abot SHOWPLAN_ALL ON. Also, i've updated my post again. I don't think i explained properly HOW i would want to search for results. Basically, i can't search by parts because i have no idea what the parts are. Can u please have another look at my intial post now that i've updated it?
      singulars
      1. PO
      1. USPure.Krome
    2. COI can't break the names into parts. why? because the user is entering this via a single search box. There's no way we can guess what is a firstname, etc.
      singulars
      1. PO
      1. USPure.Krome
    3. COcan you put in three search boxes, first, middle, and last?
      singulars
      1. PO
      1. USracer x
 

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