Using our SQL integration it is possible to display:

  • Anything SQL expressible.

Useful facts about SQL:

Update Frequency:
Every 1 minute (or custom)

Supports Custom Fields?
Yes

Supports deleted registrations?
No


How to import data from your SQL server into Plecto:

We can import from the following SQL server types:

  • MySQL
  • PostgreSQL
  • Microsoft SQL Server 2005 and later (except Azure SQL)
  • Oracle

The following fields are standard fields:

  • member_name (required)
  • member_id (required, unique identifier)
  • date (required)
  • reference (unique identifier, can be used to update registrations)
  • team_name (optional)
  • parent_team_name (optional)


Important information about the import:

  • The query: Write an SQL statement that returns a number of rows, each corresponding to a registration in our system. Each row can have any number of columns which will be saved on the registration. 
  • Historical data: Plecto can import historical data once. Then we keep the data up to date by importing every x minutes, but only the rows that has changed.
  • New data: Plecto only imports rows that have changed in the last 5 minutes (for example). This means you have to write your SQL query in such a way that it only returns the latest 5 minutes of changes. Please see below.


Remember to limit your SQL statement:

Plecto will, in each import, import all data – also data that has already been imported. Therefore, it is important to limit your statement so you do not import millions of rows of data at every import.

To speed up the updates and have a lower load on your servers, please limit your statement so it only returns the latest changed data. You can use the variable {{ last update time }} to filter out items that were not imported since the latest run.

If you have a date field, it can be done in the clause using following function:

date field >= {{ last_update_time }}


You can also use a top 100 in the 'SELECT' function, and remember to order 'DESC' (descending) to get the newest.


Update frequency:

Our system will automatically increase your SQL update frequency depending on the reply time from your server.

If the update frequency is set to 1 minute, but the import takes between 30 - 120 seconds, we will adjust the update frequency to 5 minutes.

If the update frequency is set to 1 or 5 minute, but the import takes between 120 - 180 seconds, we will adjust the update frequency to 15 minutes.

If the update frequency is set to 15 minute, but the import takes between 180 - 360 seconds, we will adjust the update frequency every 1 hour.

Did this answer your question?