In SQL Server, DROP TABLE statement deletes only the definition and tuples of a relation. It does not delete indexes, triggers, constraints, and access right specifications defined on the relation since indexes, triggers, constraints, and access right specifications may still be in use; other users and stored procedures may be using them. INNER JOIN ≡ CROSS JOIN WHERE is always TRUE.
true/false
While creating a CHECK constraint, if there are tuples violating the condition we specify as part of the CHECK constraint, “cascading” specification eliminates these inconsistencies. “cascading” specification causes all “violating tuples” to be deleted.
The “*” character used in an SQL SELECT statement means “all the tuples”.
UNION and UNION ALL combine two relations. Since UNION implementation/execution does not require “sorting”, and UNION ALL requires “sorting”, UNION performs much better (is much faster) than UNION ALL.
In SQL Server, DROP TABLE statement deletes only the definition and tuples of a relation. It does not delete indexes, triggers, constraints, and access right specifications defined on the relation since indexes, triggers, constraints, and access right specifications may still be in use; other users and stored procedures may be using them.
INNER JOIN ≡ CROSS JOIN WHERE <condition> is always TRUE.
Step by step
Solved in 4 steps