Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

OLE DB Source Conversion Error

OLE DB Source Conversion Error

OLE DB Source Conversion Error

I am using a query in my OLE DB Source to pull a date and convert it into an integer smart date key in the format yyyymmdd.  The code I am using as part of my query is


        when svc.InstallDate is Null then Null
        else cast(convert(char(8), svc.InstallDate, 112) as int)

If I run the query in the Management Studio query window, it works fine.  However, when I try to execute the package I get a fatal error: "Conversion failed because the data value overflowed the specified type".

Anyone have any ideas why it would work in MS but not as part of an OLE DB source?

RE: OLE DB Source Conversion Error

It probably doesn't like the null.  Try putting


        when svc.InstallDate is Null then '
        else cast(convert(char(8), svc.InstallDate, 112) as int)

MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible.  All it takes is a little research. (Me)

RE: OLE DB Source Conversion Error

Thanks, Mr. Denny.  I tried your suggestion and it still fails, but now with an error of "Invalid character value for cast specification."

The source data type is smalldatetime.  Other than a Null, I don't know what could be causing it to barf like this.

RE: OLE DB Source Conversion Error

Never mind.  I turn into an idiot on Friday afternoons.

The error wasn't with the SELECT statement.  The destination table didn't have an int data type.

I wish the SSIS error messages were a little easier to decipher....

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close