PowerShell Scripting to Replicate EventBrite Data to MySQL

The CData Cmdlets for EventBrite offer live access to EventBrite 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 EventBrite and the CData Cmdlets for MySQL in PowerShell to replicate EventBrite data to a MySQL database.

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

Start by setting the Profile connection property to the location of the EventBrite Profile on disk (e.g. C:\profiles\EventBrite.apip). Next, set the ProfileSettings connection property to the connection string for EventBrite (see below).

EventBrite API Profile Settings

To use authenticate to EventBrite, you can find your Personal Token in the API Keys page of your EventBrite Account. Set the APIKey to your personal token in the ProfileSettings connection property.

Collecting EventBrite Data

1. Install the module:

   Install-Module APICmdlets

2. Connect to EventBrite:

   $api = Connect-API -Profile $Profile -ProfileSettings $ProfileSettings

3. Retrieve the data from a specific resource:

   $data = Select-API -Connection $api -Table "Events"

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

   $data = Invoke-API -Connection $api -Query 'SELECT * FROM Events WHERE Status = @Status' -Params @{'@Status'='live'}

4. Save a list of the column names from the returned data.

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

Inserting EventBrite 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 EventBrite 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 EventBrite resource (Events) and to exist in the database.

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

You have now replicated your EventBrite data to a MySQL database. This gives you freedom to work with EventBrite 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 EventBrite and MySQL in PowerShell, you can pipe command results to perform the replication in a single line:

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

• If you wish to replicate the EventBrite 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-API 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')}