These are attributes of one table that have matching values in a primary key in another table, allowing for relationships between tables.
Latest Answer : Foreign Keys are keys used in a table as an attribute and are primary keys of some other table ...
Describe the elements of the SELECT query syntax. SELECT element FROM table WHERE conditional statement?
Joins, unions and nested selects are used to retrieve data.
Latest Answer : The two tables has to be linked.EXEC SQL
SELECT A.EMP_ID, B.WAGE FROM Table1 A, Table2 B WHERE A.EMP_ID = B.EMP_ID
AND A.EMP_ID = ...
A view is a virtual table made up of data from base tables and other views, but not stored separately.
Latest Answer : View is a vitual table, which do not have physical storage.we can create a view from one or more than one table(s) or view(s).if any modification is done on the base table the view is also get effected.but they are some limitations while creating ...
The database descriptor, DBD is the DB2 component that limits access to the database whenever objects are created, altered or dropped.
A synonym is used to reference a table or view by another name. The other name can then be written in the application code pointing to test tables in the development stage and to production entities
Latest Answer : Also, a Synonym is specific to the DB2 subsystem. Synonym can only access the table or view in the subsystem in which it is defined. A synonym is dropped when the table is dropped.An Alias is yet another name for a table or view. But ...
An alias is an alternative to a synonym, designed for a distributed environment to avoid having to use the location qualifier of a table or view. The alias is not dropped when the table is dropped.
Latest Answer : An alias is a logical pointer to an alternate table name. The purpose of an alias is to resolve loops in the paths of joins. In some cases, more than one alias may be necessary for a given table.Cheers,Sithu ...
A LIKE table is created by using the LIKE parameter in a CREATE table statement. LIKE tables are typically created for a test environment from the production environment.
If the base table underlying a view is restructured, eg. attributes are added, does the application code accessing the view need to be redone?
No. The table and its view are created anew, but the programs accessing the view do not need to be changed if the view and attributes accessed remain the same.
What is the cascade rule and how does it relate to deletions made with a subselect. The cascade rule will not allow deletions based on a subselect that references the same table from which the deletions are being made?
