Table differences between migrated and non-migrated databases
From IMSMA Wiki
If a database has been migrated from Legacy (at least from 2010) then some columns have been changed.
| Table | Column | Initial 6.0 DB | Migrated DB |
| translation | translation | varchar(250) | text |
| hazard | medicalfacilitylevel1 | varchar(50) | text |
| hazardinfoversion | medicalfacilitylevel1 | varchar(50) | text |
| hazard | medicalfacilitylevel2 | varchar(50) | text |
| hazardinfoversion | medicalfacilitylevel2 | varchar(50) | text |
| hazreduc | medicalfacilitylevel1 | varchar(50) | text |
| hazreducinfoversion | medicalfacilitylevel1 | varchar(50) | text |
| hazreduc | medicalfacilitylevel2 | varchar(50) | text |
| hazreducinfoversion | medicalfacilitylevel2 | varchar(50) | text |
| hazreduc | teamid | varchar(38) | varchar(50) |
| hazreducinfoversion | teamid | varchar(38) | varchar(50) |
| hazreduc | teamlocation | varchar(50) | text |
| hazreducinfoversion | teamlocation | varchar(50) | text |
I can see in the migration scripts that previously also the following columns were different.
| Table | Column |
| geopoint | pointdescription |
| impactsurvey | minehistorycomments |
| hazreduc | qacomments |
| fieldreport | reportedby |
| hazreduc | vistor |
