PowerShell Scripting to Replicate EnterpriseDB Data to MySQL

Ready to get started?

Download for a free trial:

Download Now

Learn more:

EnterpriseDB Data Cmdlets

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



Write a simple PowerShell script to replicate EnterpriseDB data to a MySQL database.

The CData Cmdlets for EnterpriseDB offer live access to EnterpriseDB data from within PowerShell. Using PowerShell scripts, you can easily automate regular tasks like data replication. This article will walk through using the CData Cmdlets for EnterpriseDB and the CData Cmdlets for MySQL in PowerShell to replicate EnterpriseDB data to a MySQL database.

After obtaining the needed connection properties, accessing EnterpriseDB data in PowerShell and preparing for replication consists of four basic steps.

The following connection properties are required in order to connect to data.

  • Server: The host name or IP of the server hosting the EnterpriseDB database.
  • Port: The port of the server hosting the EnterpriseDB database.

You can also optionally set the following:

  • Database: The default database to connect to when connecting to the EnterpriseDB Server. If this is not set, the user's default database will be used.

Connect Using Standard Authentication

To authenticate using standard authentication, set the following:

  • User: The user which will be used to authenticate with the EnterpriseDB server.
  • Password: The password which will be used to authenticate with the EnterpriseDB server.

Connect Using SSL Authentication

You can leverage SSL authentication to connect to EnterpriseDB data via a secure session. Configure the following connection properties to connect to data:

  • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
  • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
  • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
  • SSLClientCertType: The certificate type of the client store.
  • SSLServerCert: The certificate to be accepted from the server.

Collecting EnterpriseDB Data

  1. Install the module:

    Install-Module EnterpriseDBCmdlets
  2. Connect to EnterpriseDB:

    $enterprisedb = Connect-EnterpriseDB -User $User -Password $Password -Database $Database -Server $Server -Port $Port
  3. Retrieve the data from a specific resource:

    $data = Select-EnterpriseDB -Connection $enterprisedb -Table "Orders"

    You can also use the Invoke-EnterpriseDB cmdlet to execute pure SQL-92 statements:

    $data = Invoke-EnterpriseDB -Connection $enterprisedb -Query 'SELECT * FROM Orders WHERE ShipCountry = @ShipCountry' -Params @{'@ShipCountry'='USA'}
  4. Save a list of the column names from the returned data.

    $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name

Inserting EnterpriseDB Data into the MySQL Database

With the data and column names collected, you are ready to replicate the data into a MySQL database.

  1. Install the module:

    Install-Module MySQLCmdlets
  2. Connect to MySQL, using the server address and port of the MySQL server, valid user credentials, and a specific database with the table in which the data will be replicated:

    $mysql = Connect-MySQL -User $User -Password $Password -Database $Database -Server $Server -Port $Port
  3. Loop through the EnterpriseDB data, store the values, and use the Add-MySQL cmdlet to insert the data into the MySQL database, one row at a time. In this example, the table will need to have the same name as the EnterpriseDB resource (Orders) and to exist in the database.

    $data | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Orders" -Columns $columns -Values $values }

You have now replicated your EnterpriseDB data to a MySQL database. This gives you freedom to work with EnterpriseDB data in the same way that you work with other MySQL tables, whether that is performing analytics, building reports, or other business functions.

Notes

  • Once you have connected to EnterpriseDB and MySQL in PowerShell, you can pipe command results to perform the replication in a single line:

    Select-EnterpriseDB -Connection $enterprisedb -Table "Orders" | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Orders" -Columns $columns -Values $values }
  • If you wish to replicate the EnterpriseDB data to another database using another PowerShell module, you will want to exclude the Columns, Connection, and Table columns from the data returned by the Select-EnterpriseDB cmdlet since those columns are used to help pipe data from one CData cmdlet to another:

    $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name | ? {$_ -NotIn @('Columns','Connection','Table')}