- T-SQL functions to convert Strings to Tables
- Batch Process to rename multiple files using Windows DOS
- SSIS Multiple Lookups in one
- mysqldump: Got error: 2049: Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled) when trying to connect
- AHK Countdown Tooltip
A quick article on an alternative to multiple lookups in SSIS. For any SSIS developer trying to create packages that need to decode a number of values into their full name/description (eg. "M" to "Male", "Prof" to "Professor").
Our extract phase in the SSIS package takes data from a source database and puts it in staging in the exact form it came through. Our transform package will convert the data and output it to the target system. For our package to decode what "M" means, it needs to look this up in a table on the original server. We had around 12 lookups to do, so you could do this:
This is an article to demonstrate a quick step-by-step on having an SSIS package loop through a directory/folder of files in order to populate a database table. We could add each file as a separate connection manager but this is inefficient and not versatile enough to accommodate files that get added later.
I am creating an extract SSIS package intended to take a text file as its source and to populate a database table with this data. Note that this only works if all the text files to be used as source data have the same number of columns and where the column widths match.
I've adapted my real working product with an example. As my work was for a Personnel/HR project, and data confidentiality is somewhat important, some of the images will be censored or data changed in the example below.
I started getting this error:
- The task with the name "Data Flow Task" and the creation name "DTS.Pipeline.2" is not registered for use on this computer
We use a combination of MS Visual Studio 2008, 2010 and 2012. VS2008 for our old SSIS packages and VS2010 for database solutions running against SQL Server 2008 R2. We can use VS2012 for both but this requires upgrading all the packages and then making them suitable for our new SQL Server 2012 instances.
This applies to a workstation (hopefully you're not doing development directly on the server). I re-installed sql server setup, re-ran the repair to no avail. A clue came from the MS site for an older version of the pipeline in that you access the SQL Server Configuration Manager. This may not be the fix for you but it was for me:
- Open Start > All Programs > SQL Server 2012 (or your latest)
- Expand "Configuration Tools" and open "Sql Server Configuration Mnaager".
- Right-click on "SQL Server Integration Services 10.0" and select "STOP".
- Right-click on "SQL Server (SQLEXPRESS)" and select "STOP".
This article is so that I don't spend so long in googling what the TxScript referenced assembly is when creating an SSIS custom component.
This is simply the "Script Component" under "Extensions". No MSDN website said this... obvious to Microsoft staff so why should their documentation include it?
- Microsoft Business Intelligence Development Studio (BIDS) Visual Studio 2008
- Microsoft Windows 7
- Microsoft .NET Framework 3.5
- Microsoft Visual C# 2008
So like lots of people on the net, I've been given a datasource with names and addresses all in UPPERCASE. Initially, no one seemed bothered but now the request came through asking if this could be restored to a normal case, a mixture of mostly lowercase and some UPPERCASE.
I'm writing this article because other solutions on the net were either incomplete, did not work for me or simply did not match the requirements (do they ever?).
- The script must be able to be copied into other SSIS packages.
- Need the option to merely tick input column names rather than hardcode these.
- "It " should be an acronym for IT, so "IT Department" and "Director of IT".
- "O'REILLY" should become "O'Reilly" and not "O'reilly".
- "MCDONALDS" should become "McDonalds" but do not apply for "MacDonalds" because of names like "MACK" and "MACHURA".
- " and ", "la", "le", " van ", " de ", " of " and similar should remain lowercase.