Click here to Skip to main content
15,885,537 members
Articles / Programming Languages / SQL

Import Fixed Length File Data into Database Table with SSIS

Rate me:
Please Sign up or sign in to vote.
4.33/5 (4 votes)
23 Sep 2014CPOL4 min read 16.9K   444   8  
This article helps with step by step detailed information to import fixed length file data into SQL server’s database table.

Introduction

Currently, most of legacy systems are getting converted into latest technologies. For example, Mainframe systems into .NET based systems. While doing so, it is obvious that the data must be converted as well.

Generally, these legacy systems provided their data into text files with fixed length data in it.

This article helps to import the fixed length data available in the file into SQL servers Database Table with SSIS.

SSIS (SQL Server Integration Services) is an ETL (Extract-Transform-Load) tool which comes with Microsoft SQL Server.

Using the Code

I have tried to provide step by step detailed information to import the fixed length file data into SQL server database table. I have used Microsoft SQL Server 2008 R2 and Business Intelligence Studio to write the code, however it is similar to SQL server 2005 onwards and should work with minor changes.

Import Fixed Length File with SSIS

Open SQL Server Business Intelligence Development Studio

  • Select Start ->> All Programs >> Microsoft SQL Server 2008 R2 >> Business Intelligence Development Studio.

    Image 1

  • This will display the following screen:

    Image 2

  • Now to create the new project, select File Menu >> New >> Project. It will display window to select the project type and its name.
  • Select Project Type as “Business Intelligence Projects” and Template as “Integration Services Project” as shown in below window.
  • Select the project location. I have select project location as “C:\CodeProject\ImportFixedLengthFile”.
  • Enter Project Name. I have provided project name as “ImportFixedLengthFile”. Please refer to the below window:

    Image 3

  • Click on OK.
  • This will create a new project which requires reference files. And display the below screen:

    Image 4

  • Drag Data Flow Task from toolbox and drop into Control Flow:

    Image 5

  • Double click on the Data flow tasks which take you to data flow area.
  • Drag and Drop Flat file source.
  • Right click on it and select Edit. This will open window to configure source of data.

    Image 6

    Enter Connection name. I have given connection name as SourceofData.

    In General Settings, click on Browse button and select file in which data is available.

    Select Format as “Fixed width”.

    Select Advanced tab. Now here, we have to select properties of each column.

    1. For this example, I have prepared file with the below definition:
      SQL
      EmpID char(3)
      FirstName char(30)
      MiddleName char(30)
      LastName char(30)
      City char(30)
      PinCode char(6)
      
    2. Sample data available in the file is shown in the below screen shot:

      Image 7

    3. Click on Add Column, Enter Column Name, Enter Input Column Width and Enter Output column width. To keep this example simple, just provide the column name and size as given above.
    4. After entering these all column details, Connection manager column will look like this:

      Image 8

  • Click on OK.
  • Now Flat File source is available with below columns configuration:

    Image 9

  • Click on OK.
  • In the same way, we have to configure the Destination connection where the data has to be imported from above connection.
  • Drag ADO Net destination from Data flow destinations and Drop into Data flow task.

    Image 10

  • Select the Success Precedence from Flat File Source and join it with ADO Net Destination.

    Image 11

  • Now, double click on the ADO Net destination, the following window will open:

    Image 12

  • Click on New.
  • Click on New in Data Flow Connections.
  • Select Server Name as (local).
  • Select “Use Windows Authentication”. You may use SQL Server authentication if required.
  • Select Database Name where destination table is available. I am selecting CodeProject as database.

    Image 13

  • Click on OK

    Image 14

  • Click on OK.
  • Then Select Table where data has to be imported. I have existing table "dbo"."EmpDetails" with below table definition. If you do not have it, then you may create such a table.
    SQL
    CREATE TABLE [dbo].[EmpDetails]
    (
            [EmpID] [nvarchar](3) NULL,
            [FirstName] [nvarchar](30) NULL,
            [MiddleName] [nvarchar](30) NULL,
            [LastName] [nvarchar](30) NULL,
            [City] [nvarchar](30) NULL,
            [PinCode] [nchar](6) NULL
    )
  • Select preview to check if everything looks as expected. I get the below window with Preview.

    Image 15

  • Click on Mappings.
  • Check if each column is mapped with respective destination column.

    Image 16

  • Click on OK.
  • Finally, our screen will look like the below screen shot:

    Image 17

  • Right Click and select “Execute Task”.
  • Data flow task will be executed and the data available in source file will be imported into Destination. database table “EmpDetails”. After execution, the screen will look like the below screen shot:

    Image 18

  • Data flow task will be executed and the data available in source file will be imported into Destination database table “EmpDetails” and data in the table will look like is shown in the below screen shot:

    Image 19

Points of Interest

You may refer to my other topic details at http://www.codeproject.com/Articles/baliram-surya#articles

History

  • Initial draft

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Software Developer (Senior)
India India
Baliram has done B. Tech. in Information Technology from Dr. Babasaheb Ambedkar Technological University, Lonere- Raigad, MS-India . He is an interested, committed, creative Software professional having 9 years of experience Microsoft Technologies. He is working on Database conversion projects from last 4 years and prior to it worked on web / windows based solutions.

Comments and Discussions

 
-- There are no messages in this forum --