Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
simondeutsch
Aged Yak Warrior
547 Posts |
 Posted - 2002-11-21 : 12:05:58
|
| Original Post:http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=21777I am still hitting this problem, and it's a horrible headache. I just can't do a proper import. Now I'm having this problem even when splitting the large tables into smaller tables. S/O please help!Sarah Berger MCSD |
|
|
M.E.
Aged Yak Warrior
539 Posts |
Posted - 2002-11-21 : 12:56:15
|
| I've always had a horrible time with importing dates. I have several flaat files that do something simular when I import them. To handle it I've created an intermidiate table (tablename_DTS) that I load the data into. The columns on this table are really vague as far as datatypes and column names. I have a table that comes to me as key,date,commentI have a table for thiscomments_dts(c1 varchar(20), c2 varchar(30), c3 varchar(5000))I import to this table as step one of the dts package. Step 2 is the insert statement that moves data to the actual table.-----------------------SQL isn't just a hobby, It's an addiction |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2002-11-21 : 13:46:24
|
| I do the same thing as M.E.. I create a table that will hold the data. This table has vagues data types so that you can get all sorts of different data into it. Once the table is loaded, I then run stored procedures to move the data where it is supposed to be. |
|
|
|
|
|
|
Cont: Date Problems