Click on the table node to create a new table based on your data file.
Click on the table node to create a new table based on your data file.
In SQL Developer if you use the Import Data feature from the main tree node, it will create a new table based on a delimited text or Excel file.

We’ll look at the data and create some columns for you.

In version 4.1, we’ll recognize numbers as numbers, dates as dates, and try to get a best guess for you in terms of the proper date formats, precision, etc.

In all version of the tool, we scan the preview size of the input stream to figure out how big to make the text fields.

You can increase the preview window to get more accurate sizing, but the more we read, the more expensive it gets.
You can increase the preview window to get more accurate sizing, but the more we read, the more expensive it gets.

Instead of letting the import fail b/c row 101 is 30 chars long, we’re going to have some ranges in play – so that if we see the largest string is 29 characters, we’ll default the field to 50 and so on.

Now, this is where I start to worry.

Are you just putting the data into the database for some quick-n-dirty processing? I really hope so. And it makes sense, you’re creating a new table based off a spreadsheet.

But, if you’re doing some serious application work, please do a proper data model first. Talk to your business users. Gather requirements. Analyze the data structures, performance requirements, etc.

You might want this to be a partitioned table after all. Or you might want CLOBs instead of VARCHAR2s. Or your indexing scheme might not work out well with some of your choices on this wizard.

Before you do ‘quick and dirty,’ consider the guy or gal that has to come in after a few months and make it work. It will cost a lot more then than the few minutes here while you’re quickly clicking through wizard dialog pages.

Thanks for letting me preach a bit. Excel kinda makes me want to deliver sermons for some reason.

thatjeffsmith
Author

I'm a Senior Principal Product Manager at Oracle for Oracle SQL Developer. My mission is to help you and your company be more efficient with our database tools.

4 Comments

  1. I’m going to cross my fingers and hope it will be a bit smarter on column names too (like automatically uppercasing them, substituting in underscores for spaces and if it starts with a number add a alphabetic prefix.).

    • thatjeffsmith

      No actually…but the underscores for spaces and alpha prefixes are great ideas.

      But I don’t get why we’d need to uppercase them. Unless you quote them, they get created as you’d expect.

  2. Parley Kennelly Reply

    You did it again. You mentioned 4.1. I know you don’t like to give release date predictions, but is there a list of bug squashes that will be part of 4.1?

    • thatjeffsmith

      I’m talking about it, so you can assume it’s pretty close. I’m looking at the bug fixes list now..and also at the bugs I want fixed before 4.1 is released.

      We’ll do an EA (beta) and then we’ll release it for reals.

Write A Comment