RE: Field mapping on Importing
From: John Bell (JohnBell_at_discussions.microsoft.com)
Date: 11/24/04
- Next message: John Bell: "RE: Image variable in Stored Procedures"
- Previous message: Bobby: "Date Formats"
- In reply to: Paul: "Field mapping on Importing"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Nov 2004 11:09:06 -0800
Hi
If this is a repeated activity you may be better off creating a DTS job to
do it. To avoid making the datatype changes each time you could use staging
tables and just truncate them each time before loading the data. Ideally you
will have a finite number of input file formats. Varying filenames should not
be a problem see http://www.sqldts.com/default.aspx?246.
John
"Paul" wrote:
> Hi All
>
> I regularly import data from MS access databases (and many other formats) to
> SQL server using the enterprise manager. However, the DBTIMESTAMP property
> of Access gets imported as a smalldatetime in SQL server, which often causes
> problems. At the moment, I click on every table and select the DateTime
> property for each DBTIMESTAMP field before running the import. However, this
> is a pain and I was wandering if I can set the default mapping to choose
> DateTime instead either in my SQL Server, or in the individual database I
> have created to import the data into.
>
> Any help would be great... Also, if anyone knows of any cool software or
> methods for importing very different databases into my one I would love to
> know.
>
> Thanx in advance
> Joe
>
>
>
- Next message: John Bell: "RE: Image variable in Stored Procedures"
- Previous message: Bobby: "Date Formats"
- In reply to: Paul: "Field mapping on Importing"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
