We now have all our .sync files in git. There are some great code review features for sql, both human and AI, but we are unable to utlilise because the sql is encrypted. The sql encryption is a relative recent feature ie within about the last 12 months.
The ask is to not encrypt the SQL in .sync files, or at least provide an option to not encrypt or some alternative.
Reason to not encrypt the sql
1/ In git, the reviewer cannot see the before and after change without downloading the branches and opening in Phocassysnc.exe. Slows the process.
2/ We cannot apply any AI smarts to auto review eg catch poor formatting/styling or silly mistakes
3/ Change management is slowed for the same reason as point 1.
4/ There is no sensitive data in SQL, in the connection string yes but that is ok.
I agree from the simple fact that we cannot quickly scan the sync file to see the sql code if searching for specific Stored Procedure or SQL scripting. It blumming painful.
Any news on this as it is hampering our ability to find specific rogue SQL scripts which we are trying to eliminate. I.e. A view on our SQL box is causing significantly high IO and need to determine if its used in any sync feeds? Dont understand why the query has now been encypted, used to be very useful to find text in file to quickly identify the sync files where it is contained.
Thanks for bumping this @JonKemp and the original suggestion @janthony. It was a conscious decision to encrypt the sync scripts as this contains lots of Phocas IP but the product team will reach out in the next week to connect on the use case and understand more.