Ready to get started?

Download a free trial of the IBM DB2 Cmdlets to get started:

 Download Now

Learn more:

IBM DB2 Icon IBM DB2 Data Cmdlets

An easy-to-use set of PowerShell Cmdlets offering real-time access to IBM DB2. The Cmdlets allow users to easily read, write, update, and delete live data - just like working with SQL server.

Pipe DB2 Data to CSV in PowerShell



Use standard PowerShell cmdlets to access DB2 tables.

The CData Cmdlets Module for DB2 is a standard PowerShell module offering straightforward integration with DB2. Below, you will find examples of using our DB2 Cmdlets with native PowerShell cmdlets.

Creating a Connection to Your DB2 Data

Set the following properties to connect to DB2:

  • Server: Set this to the name of the server running DB2.
  • Port: Set this to the port the DB2 server is listening on.
  • Database: Set this to the name of the DB2 database.
  • User: Set this to the username of a user allowed to access the database.
  • Password: Set this to the password of a user allowed to access the database.

You will also need to install the corresponding DB2 driver:

  • Windows: Install the IBM Data Server Provider for .NET.

    On Windows, installing the IBM Data Server Provider is sufficient, as the installation registers it in the machine.config.

  • Java: Install the IBM Data Server Driver for JDBC.

    In the Java version, place the IBM Data Server Driver JAR in the www\WEB-INF\lib\ folder for this application.

$conn = Connect-DB2  -Server "$Server" -Port "$Port" -User "$User" -Password "$Password" -Database "$Database"

Selecting Data

Follow the steps below to retrieve data from the Orders table and pipe the result into to a CSV file:

Select-DB2 -Connection $conn -Table Orders | Select -Property * -ExcludeProperty Connection,Table,Columns | Export-Csv -Path c:\myOrdersData.csv -NoTypeInformation

You will notice that we piped the results from Select-DB2 into a Select-Object cmdlet and excluded some properties before piping them into an Export-Csv cmdlet. We do this because the CData Cmdlets append Connection, Table, and Columns information onto each "row" in the result set, and we do not necessarily want that information in our CSV file.

The Connection, Table, and Columns are appended to the results in order to facilitate piping results from one of the CData Cmdlets directly into another one.

Deleting Data

The following line deletes any records that match the criteria:

Select-DB2 -Connection $conn -Table Orders -Where "ShipCity = New York" | Remove-DB2

Inserting and Updating Data

The cmdlets make data transformation easy as well as data cleansing. The following example loads data from a CSV file into DB2, checking first whether a record already exists and needs to be updated instead of inserted.

Import-Csv -Path C:\MyOrdersUpdates.csv | %{
  $record = Select-DB2 -Connection $DB2 -Table Orders -Where ("Id = `'"+$_.Id+"`'")
  if($record){
    Update-DB2 -Connection $db2 -Table Orders -Columns ("OrderName","Freight") -Values ($_.OrderName, $_.Freight) -Where ("Id = `'"+$_.Id+"`'")
  }else{
    Add-DB2 -Connection $db2 -Table Orders -Columns ("OrderName","Freight") -Values ($_.OrderName, $_.Freight)
  }
}

As always, our goal is to simplify the way you connect to data. With cmdlets users can install a data module, set the connection properties, and start building. Download Cmdlets and start working with your data in PowerShell today!