The Import Wizard

Question

The Import Wizard

Steve Jones - SSC Editor

SSC Guru

Points: 737585
More actions
November 5, 2014 at 9:32 pm

#312378

Comments posted to this topic are about the item The Import Wizard
November 6, 2014 at 1:27 am

This was removed by the editor as SPAM

Viewing 15 posts - 1 through 15 (of 22 total)

You must be logged in to reply to this topic. Login to reply

Koen Verbeeck SSC Guru Points: 259155 More actions · Answer 1

I didn't notice at first why the import would fail. After all, 150 characters fit perfectly in a 200 character-wide column.

Then I remember the default for the flat file connection manager.

Great question!

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

paul.knibbs SSCoach Points: 15320 More actions · Answer 2

Just took a blind guess at this one because I've never used the wizard--I'd import a flat file using BULK INSERT and then spend hours reading through the error tables trying to figure out why it didn't work!

TomThomson SSC Guru Points: 104773 More actions · Answer 3

Good question.

It raises an issue about the quality of this wizard: why on earth doesn't it read metadata for the target table and set lengths accordingly? It shouldn't be a permissions issue, because if I can write into a table I'd better be allowed to discover the column widths. So this wizard seems poorly thought out.

Tom

Koen Verbeeck SSC Guru Points: 259155 More actions · Answer 4

TomThomson (11/6/2014)
Good question.
It raises an issue about the quality of this wizard: why on earth doesn't it read metadata for the target table and set lengths accordingly? It shouldn't be a permissions issue, because if I can write into a table I'd better be allowed to discover the column widths. So this wizard seems poorly thought out.

There is such a feature in the Advanced section. There you can click a button and it will scan the flat file and determine the column widths.

Not exactly a great solution...

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Umer Akram SSC-Insane Points: 22209 More actions · Answer 5

Nice question, it reminded me when i used this wizard 1st time for flat file :-).

Thanks for sharing.

Koen Verbeeck SSC Guru Points: 259155 More actions · Answer 6

twin.devil (11/6/2014)
Nice question, it reminded me when i used this wizard 1st time for flat file :-).
Thanks for sharing.

The problem is that only the wizard has this issue, but SSIS itself as well (because they use the same mechanisms behind the scenes). Annoying...

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Umer Akram SSC-Insane Points: 22209 More actions · Answer 7

Koen Verbeeck (11/6/2014)
twin.devil (11/6/2014)
Nice question, it reminded me when i used this wizard 1st time for flat file :-).
Thanks for sharing.
The problem is that only the wizard has this issue, but SSIS itself as well (because they use the same mechanisms behind the scenes). Annoying...

it would be off topic but anyways, when i saved the wizard package 1st time, i found the existence of SSIS.

so thanks for creating this wizard :hehe:

Gazareth One Orange Chip Points: 27737 More actions · Answer 8

TomThomson (11/6/2014)
Good question.
It raises an issue about the quality of this wizard: why on earth doesn't it read metadata for the target table and set lengths accordingly? It shouldn't be a permissions issue, because if I can write into a table I'd better be allowed to discover the column widths. So this wizard seems poorly thought out.

I agree. I wonder if it's to minimise memory used to help speed up the import.

The target is selected after the source is defined but I can't think of a reason why it couldn't recalculate the metadata once the target is selected.

Nice Q Steve, had to read it a few times before the lightbulb illuminated!

SqlMel SSCrazy Points: 2901 More actions · Answer 9

SqlMel

SSCrazy

Points: 2901

November 6, 2014 at 5:24 am

#1756952

+1

Thanks for the question.

---------------
Mel.

dlaughlin 24148 Old Hand Points: 355 More actions · Answer 10

Koen Verbeeck (11/6/2014)
I didn't notice at first why the import would fail. After all, 150 characters fit perfectly in a 200 character-wide column.
Then I remember the default for the flat file connection manager.
Great question!

Same here. I had to read it through a couple times.

stephen.long.1 SSCrazy Points: 2591 More actions · Answer 11

TomThomson (11/6/2014)
Good question.
It raises an issue about the quality of this wizard: why on earth doesn't it read metadata for the target table and set lengths accordingly? It shouldn't be a permissions issue, because if I can write into a table I'd better be allowed to discover the column widths. So this wizard seems poorly thought out.

Good point, Tom. I agree, it should work that way. That sounds like a good idea for a Microsoft Connect suggestion.

Nice question, Steve. Thanks.

SQLRNNR SSC Guru Points: 281334 More actions · Answer 12

Koen Verbeeck (11/6/2014)
I didn't notice at first why the import would fail. After all, 150 characters fit perfectly in a 200 character-wide column.
Then I remember the default for the flat file connection manager.
Great question!

+1

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Miles Neale SSChampion Points: 13147 More actions · Answer 13

Excellent question, I do not use ssis for flat files much so I was one who learned something about this today.

Not all gray hairs are Dinosaurs!

The Import Wizard

Cookies on SQLServerCentral