## test svn mirroring##
Hi all
As part of trying to make sure we keep all SQL changes up to date I've asked Simon to add a new folder to subversion. In this folder I'd suggest we do the following
1. have a folder for each release called the system name and version number. We will also need to know what order these folders were made in so I'd suggest a number at the start - something like 01-TravelCard-V1 as a folder name
2. Inside this folder put all the scripts we need to run. Again we need a numeric identifier telling us what order to run the scripts in. We also need to ensure that any tables are created with any keys, then triggers, then views, then sprocs, then data then the referential script (which clears out the costing group table and re-populates)
so table scripts should start 0(e.g. 001_ISR_SRT_standby_route.sql)
Triggers should start 1(e.g. 101_T_moo.sql)
Views start 2
sprocs start 3
data starts 4
referential always starts 99
the hole in this secuence allow us to stick other bits in when needed. I know this will seem very very confusing but it allows us to run the scripts in order. We'll see how this goes for a bit and then lets look at how else it can be done going forward
More examples.
a.Tables
i.001- Table1_PK_issue_no_12345.sql
ii.002- Table2_PK_issue_no_12345.sql
iii.003- Table3_FK_issue_no_12345.sql
b.Triggers
i.101-Trigger1_issue_no_12345.sql
ii.102-Trigger2_issue_no_12345.sql
iii.1031-Trigger3_issue_no_12345.sql
c.Views
i.201-View 1_issue_no_12345.sql
ii.202-View 2_issue_no_12345.sql
iii.203-View 2_issue_no_12345.sql
d.Stored Procedures
i.301-Stored procedure 1_issue_no_12345.sql
ii.302-Stored procedure 2_issue_no_12345.sql
iii.303-Stored procedure 3_issue_no_12345.sql
e.Data scripts
i.401- Table1_PK_issue_no_12345.sql
ii.402- Table2_PK_issue_no_12345.sql
iii.403- Table3_FK_issue_no_12345.sql
f.Referential Data
i.991- Table1_FK_issue_no_12345.sql
ii.992- Table2_FK_issue_no_12345.sql
iii.993- Table3_FK_issue_no_12345.sql
Cheers
16/05/13