Needed help to add columns from one table to another table

Question

Hi,
I have emp and dept tables. I think most of all might know what columns it's contain. Now I want to create table emp_dept with all emp and dept table columns.
I have wrote the below query it's worked too. But I think there should be some more other queries to get accomplish the same task. Plz let me know.
create table emp_dept as select a.*, b.dname, b.loc from emp a full outer join dept b on a.deptno = b.deptno where 1=2
Thanks for your time..

Answer 1

Hi,
1004909 wrote:
Hi,
I have emp and dept tables. I think most of all might know what columns it's contain. Now I want to create table emp_dept with all emp and dept table columns.
I have wrote the below query it's worked too. But I think there should be some more other queries to get accomplish the same task. Why do you think that?
Plz let me know.
create table emp_dept as select a.*, b.dname, b.loc from emp a full outer join dept b on a.deptno = b.deptno where 1=2"WHERE 1 = 2" means you want to create the table, but not put any rows in it. In that case, theere's no need for a full outer join; a simple inner join would do just as well.
There is no single "right" or "best" table. (Most of us would have differerent jobs if there were.)
It does, however, make sense to talk about the "right" or "best" table for some specific purpose .
The emp and dept tables in the scott schema are great for transaction processing, where rows are frequenctly INSERTed, UPDATEd and/or DELETEd. For example, if department 10 moves from New York to Pune, you only have to find and UPDATE 1 row, and that one UPDATE will affect all employees in departemnt 10, regardess of how many there are.
What purpose will the emp_dept table have? Why is the table design used in the scott schema not best for you?
One possibility is that you need a tale that is very fast to query, even though it may be very inefficient for transactions. For example, you might want a data warehouse that is only refreshed once a day, and were you can run several common queries quickly, without joining the emp and dept tales.
Another possibility is that your data model (that is, what are the entities and the attributes) is different. For example, you may have a model where employees King and Miller both work in department 10, but King's location is New York, but Miller's is Pune.
In either of these situations, the table you posted migt be the best design. Why are you asking the question? What is the problem with the emp_dept table you posted?