OneTrack can store SQL changes that you make to your development database whilst you develop. Allowing you to later export a single SQL file that updates your production database.
There are 5 areas that SQL can be stored within:
From the SQL tab, click the "Edit" button to see the stored data.
The main window will then update to show the SQL Editor:
Enter your SQL changes within the appropriate tab. For SQL that doesn't fit into any of the defined categories, you can place it under the "Misc" section. SQL placed under the incorrect section will still work perfectly fine, however the export feature generates the SQL based upon these sections. So readability may be hindered if you disregards the sections.
Ensure you always end your statement with the semi-colon; - as this is how OneTrack counts how many of each statement kind you have.
Single Issue Export
Should you only require the SQL changes from one single issue, you can quickly export at any time by using the "Export" button. This will generate your SQL file ready for use on your database.
An example of a generated SQL file (viewed in a editor):
OneTrack can also generate a SQL file that encompasses all of the resolved issues within a milestone. This can be actioned from the Reporting menu:
Select the milestone you wish to export and then simply click the "Export" button and save the file. An example of a exported milestone SQL file is pictured below, with two styles of typing SQL:
As default "FOREIGN_KEY_CHECKS" is included with exported files. You can change this from the OneTrack settings.