Dts Problem!

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mayati
    New Member
    • Jul 2006
    • 5

    #1

    Dts Problem!

    Hello Everyone,

    I have a DTS package, which has been working fine for few years. it runs once a month to get information from different databases and save it into the destination database. Now I get this error:

    error source: microsoft ole db provider for sql server
    error description: could not get the data of the row from the ole db provider 'MSOLAP'.
    Conversion failed because the data value overflowed the data type used by the provider.
    OLE DB error trace[OLE/DB provider 'MSOLAP' IRowset::GetDat a returned 0x40eda: Data status returned from the
    provider:[COLUMN_NAME=[Measures].[The profit]STATUS=DBSTATUS _EDATAOVERFLOW], [COLUMN_NAME=[Measure].[Hours T2]

    Any help will be apreciated!
  • iburyak
    Recognized Expert Top Contributor
    • Nov 2006
    • 1016

    #2
    Your source table has data that is not acceptable on your side.
    It could be just for example if you have int column and source table has bigint. All this time all numbers where easily converted into int datatype on your server but now one of the numbers is too big for your table and you get overflaw error .
    Basically your message says that datatype on the source table can’t be accepted on destination. Try to load data into a work table where all columns are character datatype and view what is not convertible into datatypes on your table.

    Unfortunately solution involves some research on your part.


    Good Luck.

    Comment

    • mayati
      New Member
      • Jul 2006
      • 5

      #3
      Thank you for your reply,

      The problem is I know that the destination table has numeric datatype but the data comes from a cube on an OLAP linked server, I looked att som values there som was numerics and others '-1,#j' probably a formuler results. and I do this convert(float, "[Measures].[ The profit]"). What else do I need to do?

      Comment

      • iburyak
        Recognized Expert Top Contributor
        • Nov 2006
        • 1016

        #4
        As I already said.
        Load data into a work table where this column is a character datatype and add additional step to your DTS package where you filter out unwanted records while loading data into production table. This way you can have exception table where you will enter invalid records and see what could be done to fix them.


        Good Luck.

        Comment

        Working...