DDX for SQL - Technical Specification


The Daily Data Extractor (DDX) is an installable software application. 

Its purpose is to securely transfer data from a ticketing system database to the Purple Seven Server over an internet connection. 

The purpose for which you send us your data will change from time to time, but Purple Seven will only process your data in accordance with the written instructions provided by you through a formal Statement of Work.


  • The DDX operates on a regular basis determined by a Windows Service created on the same machine on which the DDX is installed.  
  • It is required that the application is opened using Administrative privileges
  • On activation, the DDX contacts the Purple Seven Server to receive SQL scripts to run against the ticketing database.  
  • The DDX then transmits the resultant data back to Purple Seven’s server. 
  • The DDX can also be manually initiated through the application control panel. 



Configurable Connection String to the SQL database

Operates over the network (LAN or WAN) 

Windows Service activation

Activation of the DDX is triggered by a Windows Service at a time defined within the application by the user

Configurable SQL Extraction 

The data to be extracted is determined by the queries sent from the Vital Statistics Server on Activation 

Full Logging functionality 

The DDX operates a dual logging procedure.  There is a local logging file which logs all activity by the DDX accessible from within the application itself, and a remote logging procedure which documents all contact with the Purple Seven Server. 

Bandwidth management 

The extracted data is transferred to the Purple Seven server in packages.  Each package contains a number of rows.  The size of each packet is determined by the type of box office system.  This functionality allows the approximate bandwidth used to be managed. 

Proxy Server Security Support 

If your network uses a Proxy Server, the DDX can be configured to support it. 


The DDX is a simple Windows Forms application developed in VB.NET.  It is designed to be installed directly on a server or PC that:

  1. can connect via connection string to the SQL Server database where the ticketing data is stored and,
  2. has access to the internet. 

The DDX uses the standard port 443 for its SSL / TLS tunnelling. Usually no alterations or special ports should need to be opened. 


The DDX For SQL is compatible with the following ticketing systems: 

  • Audience View 
  • Bravo Solution
  • Enta 
  • Patron Base 
  • SRO (Blackbaud, TopTix, the Patrons Edge)  
  • Tessitura 
  • VenueMaster 
  • Wembley 

We also have a DDX for Web that includes compatibility with some of the major web based ticketing systems or a DDX for Flatfile that enables you to send your data through text files.  Please contact us for more information about these systems.



  • Microsoft Windows 10
  • Microsoft Server 2012 or later


  • Client (a computer not working in a server capacity): 90-megahertz (MHz) Intel Pentium- class processor or an AMD Opteron, AMD Athlon64 or AMD Athlon XP processor or better. 
  • Server (a computer working in a server capacity): 133-MHz Intel Pentium-class processor or an AMD Opteron, AMD Athlon64 or AMD Athlon XP processor or better. 


  • Microsoft Internet Explorer 5.01 or later 
  • .NET Framework 4.5


  • 110 MB of hard disk space required, 40 MB additional hard disk space required for installation (150 MB total)  


The data is sent via a TLS /  SSL tunnel to a web service hosted on our secure.purpleseven.com domain, which is secured by a Sectigo certificate providing SHA256 bit encryption. 

If you need to configure a firewall or whitelist access to our servers, then allow outbound connections to on port 443.


The resources used by the DDX are dependent on a number of factors (such as PC specification, ticketing system, network and internet speed) which cannot be easily predicted and organisations of different sizes will have different resources available to them.   

For example, a ticketing consortium may well have a fast connection to the internet which will reduce the time it takes to transfer the data compared to a mid-sized organisation which may have an ordinary broadband connection.

The SQL scripts are normally authorised by each ticketing system supplier and you should contact your supplier to ensure that the scripts for your system have been authorised by them.  Scripts are written to use indexed fields to filter the data. This increases speed and reduces processor overhead.   Custom scripts can be developed on request (usually at a charge).  The following details the average extract and upload time: 

Organisation Size 

Annual Ticket Volume 

Average Time (mins) 

Small organisation 

Up to 100,000 


Medium Organisation 

Under 1 million 


Large organisation 

Over 1 million 



Over 2.5 million 



Once installed, the DDX requires little ongoing maintenance.  The following summarises the more common circumstances where administrative support may be required: 

  • Change of Ticketing System 
  • Change of Security Information (i.e. the password of the SQL Server User has changed) 
  • The computer the DDX is installed on is changed in a significant way (i.e. its physical location moves or it no longer has network access to either the ticketing database or the internet )
  • The login details to the Proxy Server change from that used in the DDX 
  • The SQL server name or database name change 

Upon installation, the DDX creates a new set of Registry Keys in the following path: 


These keys are used to record the status of the DDX uploads.  The DDX reads from and writes to the Registry every time it is activated so the User who will be ‘running’ the DDX will need permission to write to the Registry.   The permissions can be set separately, but Administrator rights are required to undertake the installation. 

The DDX never writes to the SQL Server databases; it is a read only operation and you can enforce this through the permission you provide the DDX through the SQL Server Authentication. 

If the operation of the DDX is interrupted, e.g. by an internet failure or the machine the DDX is installed on is shut down, the DDX will collect data from the date it last successfully updated data (unless these settings are overridden by Purple Seven staff). 


The DDX will extract the fields as defined in the SQL scripts executed against your database.   

Typically the DDX will extract the following types of data: (As the exact fields change for each Booking System and on occasion we are asked to modify the scripts on a per client basis the following should be used for guidance only). 

  • Customers records (name and contact details) 
  • Ticket Records (seat location, price, discounts and price types) 
  • Performance records (date and time and capacity of performance) 
  • Event / Run records (name and location of run) 
  • Customer and event categorisation records (e.g. Artforms / interest codes) 
  • Memberships records (membership type, start / end dates, price) 
  • Donation summaries (who, how much, when)
  • Subscription Data (who, which package, how much etc)

The above is a summary of types of data we collect.  If you would like the exact fields you can either:

  1. view the scripts that will be run against your system from within the DDX application or;
  2. Contact Purple Seven.


The DDX must be installed on a PC or Server that can connect, through a connection string, to  the SQL Server database where your ticketing data is held.   Detailed instructions can be found here


To contact Purple Seven about the DDX: 

Email: [email protected]


Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.