bit field crazyness

• mark lake

  Say Hey Kid

  Points: 702

  More actions

  October 4, 2006 at 2:43 am

  #169963

  Hi,

  I'm in the process of upgrading from 2000 to 2005.  So far so good.  But now I've encountered a strange problem...

  extracting a bit field in the management studio returns a 1 or a 0... just what I'd expect

  But in the SSIS I've designed it insists on pulling out a True or a False... which is a bit of an issue when I'm then moving the data into an Oracle database that's expecting a 1 or a 0.

  Does anyone have any clue as to why this is happening?  Obviously I can work around it but I kind of want these new SSIS' to be nice and "clean" from work arounds when I don't see a reason for this to happen

  Thanks very much in advance...

   

• Ian Griffiths

  Ten Centuries

  Points: 1025

  More actions

  October 5, 2006 at 9:18 am

  #664348

  The bit type is treated more like a Boolean in SQL2K5, you can now use 'True' and 'False' in queries as well as 1 and 0.  Can you use a cast or a case statement to get around your problem?

• mark lake

  Say Hey Kid

  Points: 702

  More actions

  October 9, 2006 at 6:02 am

  #664768

  Aye...

   

  I had the cast/case statement ready as my work around... I was hoping for an answer that was more of a setting but nevermind...

   

  Thanks very much for your help

   

  Mark