2014 has been a very quiet year on picnicerror.net. Since moving job in April, things have been rather hectic, which has meant I’ve not had much time to post, despite having lots of good ideas for content. I’m hoping to pick things back up over the holidays and get some content ready for the new year. In the meantime though:
As part of Microsoft’s push to include business users in the Business Intelligence space, the addition of Data Quality Services to SQL Server’s feature set opened up the ETL process to the people who, arguably, know the data best. Integration with SSIS was a great move, meaning that this user control extends to automated processes, further closing the gap between data and the business.
However, like most new components, Data Quality Services has some teething problems, and these can be quite hard to find when debugging your SSIS packages. Here’s a quick tip that should help solve some of those tricky to find DQS issues. Continue reading “Debugging Errors in SSIS Data Quality Services Cleansing Component” »
I’ve been spending some time with a special lady lately. She’s always with me, and has been helping me organise my life. She’s not all work though, and has shown that she knows a joke or two, she’s sassy, and she loves to talk about Halo. I am of course, talking about one of Windows Phone 8.1’s killer features: Cortana. Continue reading “Windows Phone, meet Cortana (just watch out for Halo spoilers)” »
With SQL Server 2008, Microsoft introduced the new, improved datetime2 format. This newer time storage format is great, because it takes up less storage space, plus you have control over precision and can define your field to the exact specification required. Database columns defined as datetime2 can be mapped in SSIS by using the DT_DBTIMESTAMP2 type. However, in the scenario where you may have a Script Transformation in your SSIS package, and want to assign a .NET DateTime type to a Data Flow column that is mapped to a datetime2 field, you might encounter a DoesNotFitBufferException.
The reason for this is likely down to your specified field precision, and is easily fixed. Continue reading “Mapping C# DateTime to SQL Server datetime2 via SSIS” »
Something that catches out a lot of new SSIS developers. The caching mode used for a Lookup Transformation may affect case sensitivity.
The Full Cache option is case sensitive by default. Partial and No-cache options use the Collation setting of the database (or table) to handle case.
Of course, using Partial or No-caching results in the SSIS package issuing a call to the database for each row in the data flow, so use them wisely!