SSIS - SQL Server BIGINT doesn't map to INT64 - by Phil Brammer

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 260967 Comments
Status Closed Workarounds
Type Bug Repros 9
Opened 3/2/2007 8:51:04 AM
Access Restriction Public


When setting a variable up in SSIS and setting it to an INT64 data type, returning a bigint value from SQL Server 2005 does not map correctly to this variable type even though it should.

Sign in to post a comment.
Posted by David DeLella on 7/1/2013 at 1:29 PM
7/1/2013 and apparently this issue is still not fixed. They must be way behind on that work list. I also tried to assign the bigint to a string and received the same message. Using SQL Server 2008 R2 with the latest service pack.
Posted by Gogula on 6/15/2010 at 10:51 PM
This issue still seems to be there on SQL Server 2008 (with SP1).
Posted by Microsoft on 4/5/2007 at 11:23 AM
I apologize in the delay for my reply - I didn’t see your response until now.

When an issue reported through Connect turns out to be bug, we log a new defect in our internal system, and the original is closed. Having a closed status doesn’t mean the issue has been fixed, but we do keep track of the history in the new defect report.

We can’t guarantee that a fix will make it into a particular release, but yes, this issue is on the work list for Katmai.
Posted by Phil Brammer on 3/14/2007 at 9:27 PM
So as a result of this being closed (fixed) does this mean the next release will have this corrected? This issue can't die unless it's in the work list for the next release.
Posted by Microsoft on 3/13/2007 at 5:58 PM

I’ve looked into this issue and found out some of the history behind the handling of the BIGINT type. At the time we implemented this functionality, there were issues supporting the Int64 data type across platforms. It was decided to return these values are strings instead.

Unfortunately, simply changing the behavior would break existing packages which expect BIGINTs to be returned as Strings. We are currently investigating alternatives, and will consider this fix for the next release.

Thank you.