Field mapping on Importing
From: Paul (zammit_joe_at_hotmail.com)
Date: 11/24/04
- Next message: Lubor Kollar: "Re: Partitioned view on two columns"
- Previous message: Scott Morris: "Re: Partitioned view on two columns"
- Next in thread: John Bell: "RE: Field mapping on Importing"
- Reply: John Bell: "RE: Field mapping on Importing"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Nov 2004 16:55:22 -0000
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: Lubor Kollar: "Re: Partitioned view on two columns"
- Previous message: Scott Morris: "Re: Partitioned view on two columns"
- Next in thread: John Bell: "RE: Field mapping on Importing"
- Reply: John Bell: "RE: Field mapping on Importing"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
