Post reply

Import Mdb to sqlserver 2008 Viz script's

  • July 2, 2012 at 11:48 pm

    #258744

    HI ;

    I have to import the MS-access Database .mdb File to sqlserver 2008 R2 VIA (scripts)

    My question is

    There are two databases

    1. Source database -- > Imported Mdb File database Example Source_db

    2. Destination database --> My database (Existing DB) Example destination_db

    I want update the source database tables to destination database .

    In this case some of the errors while updating tables.in destination database ..how can i get the error's in tables format and also particular table name and columnvalue are bind the tables Error table

    1.String or binary data would be truncated.

    2.Conversion failed when converting character string to smalldatetime data type.

    3.The conversion of char data type to smalldatetime data type resulted in an out-of-range smalldatetime value.

    4.The conversion of the varchar value '2357812962' overflowed an int column. Maximum integer value exceeded.

    5.Conversion failed when converting the nvarchar value '106945A5' to data type int.

    Example

    Destination Table Format

    dt_sample

    column_name datatype Length

    id INT 4

    State CHAR 2

    Table_name : Error_Table

    id Table_name , Column_name , Error_msg , Column_value

    1 dt_sample State Conversion failed when converting the nvarchar value '106945A5' to data type int. 106945A5

    1 dt_sample State String or binary data would be truncated.. FAZ

    Any one help to solve the logic .

    Thanks

    FA

    DE

  • July 5, 2012 at 8:18 am

    #1509144

    I have the same problem with Oracle data. The way I deal with it is to pull the data into staging tables, and the columns are all string data types. I am using BULK INSERT to pull the .csv data into the staging area, so putting the data into string data types is easy.

    Then I can run exception reports on the staging data to see if there are any issues with the data before I move the data to the final tables, of course, modifying the data as it goes in (converting the string to the datetime datatype, for instance).

    This allows the cleanup of the information, and the running of exception reports for the data that can't be cleaned.

    Just a suggestion.

Viewing 2 posts - 1 through 1 (of 1 total)

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