Q
Problem solve Get help with specific problems with your technologies, process and projects.

Splitting columns into separate tables

I have a table with 50 odd columns of integer type and another 20 narrative columns of type varchar2(4000). What would be the ideal design for this?

I have a table with 50 odd columns of integer type and another 20 narrative columns of type varchar2(4000). What...

would be the ideal design for this?

Option 1
Have all the columns in the same table
Option 2
Split the row. Have a separate table for the narrative, 20 columns for the narratives and one column referencing the primary key to the main table.
Option 3
Put the narratives in a separate table. However instead of one column for each narrative it would have one column for narrative type and one for the narrative (going down versus across).

Any help would be greatly appreciated.

Definitely Option 3. You might also want to apply the same logic to the 50 integer columns, if they too are "sort of all the same type of thing."

This was last published in February 2006

Dig Deeper on Oracle and SQL

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close