Frequently Asked Interview Questions

SQL Interview Questions on JOINS

char[(n)] - Fixed-length non-Unicode character data with length of n bytes. n must be a value from 1 through 8,000. Storage size is n bytes.
nvarchar(n) - Variable-length Unicode character data of n characters. n must be a value from 1 through 4,000. Storage size, in bytes, is two times the number of characters entered. The data entered can be 0 characters in length
varchar[(n)] - Variable-length non-Unicode character data with length of n bytes. n must be a value from 1 through 8,000. Storage size is the actual length in bytes of the data entered, not n bytes. The data entered can be 0 characters in length.
128 bit.
To ensure uniqueness across machines, the ID of the network card is used (among others) to compute the number.
Text and image. Use text for character data if you need to store more than 255 characters in SQL Server 6.5, or more than 8000 in SQL Server 7.0. Use image for binary large objects (BLOBs) such as digital images. With text and image data types, the data is not stored in the row, so the limit of the page size does not apply.All that is stored in the row is a pointer to the database pages that contain the data.Individual text, ntext, and image values can be a maximum of 2-GB, which is too long to store in a single data row.
Sometimes we have to select data from two or more tables to make our result complete. We have to perform a join.

Joins can be categorized as:
  • Inner joins (the typical join operation, which uses some comparison operator like = or <>). These include equi-joins and natural joins.
    Inner joins use a comparison operator to match rows from two tables based on the values in common columns from each table. For example, retrieving all rows where the student identification number is the same in both the students and courses tables.
  • Outer joins. Outer joins can be a left, a right, or full outer join.
    Outer joins are specified with one of the following sets of keywords when they are specified in the FROM clause:
  • LEFT JOIN or LEFT OUTER JOIN -The result set of a left outer join includes all the rows from the left table specified in the LEFT OUTER clause, not just the ones in which the joined columns match. When a row in the left table has no matching rows in the right table, the associated result set row contains null values for all select list columns coming from the right table.
  • RIGHT JOIN or RIGHT OUTER JOIN - A right outer join is the reverse of a left outer join. All rows from the right table are returned. Null values are returned for the left table any time a right table row has no matching row in the left table.
  • FULL JOIN or FULL OUTER JOIN - A full outer join returns all rows in both the left and right tables. Any time a row has no match in the other table, the select list columns from the other table contain null values. When there is a match between the tables, the entire result set row contains data values from the base tables.
  • Cross joins - Cross joins return all rows from the left table, each row from the left table is combined with all rows from the right table. Cross joins are also called Cartesian products. (A Cartesian join will get you a Cartesian product. A Cartesian join is when you join every row of one table to every row of another table. You can also get one by joining every row of a table to every row of itself.)
  • A table can be joined to itself in a self-join.
    A join selects columns from 2 or more tables.
    A union selects rows.
    Code Example 1:
    select o.name, i.name
    from sysobjects o, sysindexes i
    where o.id = i.id

    Code Example 2:
    select o.name, i.name
    from sysobjects o inner join sysindexes i
    on o.id = i.id
    You will not get any performance gain by switching to the ANSI-style JOIN syntax.
    Using the ANSI-JOIN syntax gives you an important advantage: Because the join logic is cleanly separated from the filtering criteria, you can understand the query logic more quickly.
    The SQL Server old-style JOIN executes the filtering conditions before executing the joins, whereas the ANSI-style JOIN reverses this procedure (join logic precedes filtering).
    Perhaps the most compelling argument for switching to the ANSI-style JOIN is that Microsoft has explicitly stated that SQL Server will not support the old-style OUTER JOIN syntax indefinitely. Another important consideration is that the ANSI-style JOIN supports query constructions that the old-style JOIN syntax does not support.
    Derived tables are SELECT statements in the FROM clause referred to by an alias or a user-specified name. The result set of the SELECT in the FROM clause forms a table used by the outer SELECT statement. For example, this SELECT uses a derived table to find if any store carries all book titles in the pubs database:
    SELECT ST.stor_id, ST.stor_name
    FROM stores AS ST,
    (SELECT stor_id, COUNT(DISTINCT title_id) AS title_count
    FRoM Sales
    GROUP BY stor_id
    )AS SA
    WHERE ST.stor_id = SA.stor_id
    AND SA.title_count = (SELECT COUNT(*) FROM titles)

    Most Visited Pages

    Home | Site Index | Contact Us