utilizing JS to write out sql, sql scripts managed by flyway
work with proper keys for joins
Dale - James thought we might put results in excel so excel tab for each table so tables create definitions
documentation - practice of updating data model
coverage codes - json, states, can upgrade json from excel, converted from json to excel, config doc + js file
tools - bolt ons on top of db
Joseph: FlyWay
<demo>
containerization from dev side
FlyWay - great db management tool, as a container
FlyWay has versioning schematic - they went with semantic version
maintains version control
containers will make it easier
operationally what the data model will drive
educating carriers to do this
ran earlier, can stop it, migrates all of these
can do it in source control
Flyway effectively does checksum on every file, maintains data integrity
parallel for EP schema?
EP written by dev, could set up repo and put in flyway to keep EPs, but each EP should be kept in Git somewhere, not re-ran, on ledger best ref point
2 parts - creation of EP schema, other is
Mason analytics
peter task: write simple sql tables for lines of business
get idea of where we are, what completed, map out getting tables up and running will look like
personal auto, went thru, 33 tables needed to bring over to use
GT2
most tables from statplan directly
some stat plans have mult lines of business
some repeatability in categories, found things in stat plan, not which need table to be integrated
more breakdown of how each stat plan is looking to keep account of
201 tables out of all stat plans
completed 99 of 201
view of how this is looking for timing and expectations
code tables - take codes and give description
for each code that comes in we need a ref table, and we need a way to decode, load, make script for each table and view, put in flyway, allow easy managed db across all these areas
codes across diff business lines the same? very few to none
none can be skipped w/o thorough review
coverage codes - lot of copy-paste
will speed up a lot as they get going, not as much overlap as you think
transaction code would have secondary key as line of biz?
opportunity to do analysis across lines of business
look out for it in a few places, def opportunity for cross-lines
have to get to next level beyond what Mason showed - data dictionary for all of them
intern request
can do it for tables named the same across lines, see where they lined up
version zero - can change anything we want and what a good releaser looks like
goal for this week - get auto coverage report gen again based on high end ETL decode job
Architecture Decision Capture Process (KenS) - Discussion