Tag: databases

0

30000

25000

35000

3500,5000,2500

5000,2850

2850,5750

5000,5750

To protect some of the columns of a table from other users

Occupies data storage space

To hide complexity of a query

To hide complexity of a calculations

SELECT dept_id, job_cat, MAX(salary) FROM employees WHERE salary > MAX(salary);

SELECT dept_id, job_cat, MAX(salary) FROM employees GROUP BY dept_id, job_cat;

SELECT dept_id, job_cat, MAX(salary) FROM employees;

SELECT dept_id, job_cat, MAX(salary) FROM employees v

SELECT dept_id, job_cat, MAX(salary) FROM employees GROUP BY dept_id, job_cat, salary;

Yes

No

NA

na

ALWAY

S ALWA

ALWAYS

None of the above

Yes

No

NA

na

CREATE

ALTER

ALTER SESSION

None of the above

Will

Wont

NA

na

Scott can create a synonym for the EMP_DEPT_LOC_VU by using the command CREATE PRIVATE SYNONYM EDL_VU FOR mary.EMP DEPT_LOC_VU; then he can prefix the columns with this synonym.

Scott can create a synonym for the EMP_DEPT_LOC_VU by using the command CREATE SYNONYM EDL_VU FOR mary.EMP_DEPT_LOC_VU; then he can prefix the columns with this synonym.

Scott can create a synonym for the EMP_DEPT_LOC_VU by using the command CREATE LOCAL SYNONYM EDL_VU FOR mary.EMP DEPT_LOC_VU; then he can prefix the columns with this synonym.

Scott can create a synonym for the EMP_DEPT_LOC_VU by using the command CREATE SYNONYM EDL_VU ON mary(EMP_DEPT_LOC_VU); then he can prefix the columns with this synonym.

Scott cannot create a synonym because synonyms can be created only for tables.

Scott cannot create any synonym for Mary's view. Mary should create a private synonym for the view and grant SELECT privilege on that synonym to Scott.