As mentioned in https://github.com/MobilityData/gtfs-realtime-validator/issues/56, when we try to deploy the validator as-is as a hosted service the default embedded HSQLDB database performance degrades with usage to the point that is it not usable. To fix this, we need to deploy a different database server (e.g., MySQL, Microsoft SQL Server, PostgreSQL).
Work to to make the validator compatible with Microsoft SQL server has been started in PR#323 on the CUTR-at-USF GitHub repository. We recommend leveraging the work already done, merging it on the CUTR-at-USF GitHub repository and then fetching the changes here.
As mentioned in https://github.com/MobilityData/gtfs-realtime-validator/issues/56, when we try to deploy the validator as-is as a hosted service the default embedded HSQLDB database performance degrades with usage to the point that is it not usable. To fix this, we need to deploy a different database server (e.g., MySQL, Microsoft SQL Server, PostgreSQL).
Work to to make the validator compatible with Microsoft SQL server has been started in PR#323 on the CUTR-at-USF GitHub repository. We recommend leveraging the work already done, merging it on the CUTR-at-USF GitHub repository and then fetching the changes here.