Just noticed that Bigint has been fixed in SSIS 2008

I mentioned the other day that I am in the beating as it is of a project with SSIS 2005.  Funny that about the time I blogged, a friend who I worked with on a large project put in his MSN messenger sigline..."SSIS 2005 can be described as frail".  The term 'frail' is spot-on in my book - I'm just amazed how much cleaner SSIS 2008 is over it's counterpart. The product IMHO is still very much in its' infancy compared to the datastages and informaticas of the world, but at least it isn't as bad as it was.  Anyway, off the soapbox. 

In the 2005 version you had to map a BIGINT as a STRING in certain tasks, such as the ExecuteSQL task. When I run the below I get the error message which I refer to:

 

 

 

 

If we go ahead and run in SSIS 2008, but change the var type to Int64, we're gold. Check it out:

 

Thanks,
Lee

 

-----------------------

Move in, now move out, Hands up and hands down, Back up, Back up, Tell me what you're gonna do now!

 

[Execute SQL Task] Error: An error occurred while assigning a value to variable "BigVar": "The type of the value being assigned to variable "User::BigVar" differs from the current variable type. Variables may not change type during execution. Variable types are strict, except for variables of type Object. ".  

 

 

 

 

 

 

 


blog comments powered by Disqus

by Lee Everest, M.S.

Poll

Do you use Azure or cloud in your organization?



Show Results

Ads

Search


Month List

Calendar

«  February 2012  »
MoTuWeThFrSaSu
303112345
6789101112
13141516171819
20212223242526
2728291234
567891011
View posts in large calendar

Tags

Disclaimer
The opinions, code, examples, et.al. expressed herein are my own personal opinions and do not represent my employer's view in any way, shape form, or fashion.  All code for demonstration purposes - no guarantees, either written or implied, are made.

© Copyright 2012 Lee Everest's SQL Server, etc. weblog