SSIS
Get flash to fully experience Pearltrees
Case How do you create a new Guid column in SSIS? Solution There is no SSIS function for that, but there are a few workarounds. A) If you already have a valid GUID in your source, but it's still a string type, then you can use a Derived Column to create a real guid. B) If your source is a SQL Server table, you can use the TSQL statement to generate a Guid column.
Create a GUID column in SSIS
Task Create a SQL Server Integration Services (SSIS) package that accepts a Globally Unique Identifier (GUID) as a variable and uses this variable as: A parameter for a SQL Server stored procedure executed via an Execute SQL Task A parameter for a SQL Command executed via an OLE DB Source Data Flow Problem
Fun with SSIS and {GUID’s} - Mr Wharty's Ramblings
01. using System; 02. using System.Data; 03. using Microsoft.SqlServer.Dts.Pipeline.Wrapper; 04. using Microsoft.SqlServer.Dts.Runtime.Wrapper; 05. using System.Data.SqlClient;
SSIS - Script Component as Source ADO.NET - Sudeep's Domain
Ok, I've played with SSIS for a while and done a lot with it, but now I am encountering something I am sure that has a simple solution... Ive got a flat text file with say the content like so Category is just literal strings etc, however I'd like to normalize that data. So I was goign to try and get a lookup or insert... as described at the url: Lookup Pattern: Key Generation
Normalizing data with Lookup or Insert
Recently Mag (surname withheld :) from California contacted me with a few queries around a package that she was building. The package was a straightforward fact table load that required to use the dimensional natural keys in the fact data to get the corresponding surrogate keys from the dimension tables. All pretty simple stuff right? Well unfortunately Mag was loading 2.5million rows of fact data and it was taking far far too long. After a fairly lengthy email exchange it transpired that Mag was using MERGE JOIN components in the pipeline to get the surrogate keys and eventually we agreed it would be best to try using LOOKUP components instead. Well Mag did just that and its not hyperbole to say that the performance improvement she got was stupendous.
LOOKUPs instead of MERGE JOINs
Integration Services, which replaces Data Transformation Services (DTS) in SQL Server 2005, is a wonderful tool for extracting, transforming, and loading data. Common uses for Integration Services include: loading data into the database; changing data into to or out from your relational database structures; loading your data warehouse data; and taking data out of your database and moving it to other databases or types of storage. This article describes how you can use the new features of SQL Server 2005 Integration Services (SSIS) to load an Excel file into your database. Note: There are several wizards that come with SQL Server Management Studio to aid you in the import and export of data into and out of your database. I will not look at those wizards; I will focus on how you can build a package from scratch so that you don’t have to rely on the wizards.
Import an Excel file into SQL Server
