@darkmatter said:Except they fixed it by prepending shit to a GUID, which makes it a varchar of some sort, which would break the SSIS package as well. So I doubt that is the issue...
And herein lies the bedrock of my WTF post. So even if we can't increase the number of columns, we end up changing the meaning of others, and changing their data type as well.
Oh, and yes, this is SSIS. Sure, SSIS falls over if you change the schema. This was confirmed by my buddy at the office, since my SSIS experience is limited.
So instead of only refreshing the schema to use a new column (which they would need to do anyway if you change a UniqueIdentifier to VarChar), they now have to add some work to break the ClientType-ClientGuid hybrid apart. Very unnecessary IMO...
And this is brand spanking new stuff, so the other WTF is why they could not just change it to accommodate their request to receive more columns...