Hi Guys,

I obviously want my modules to be marked as Azure compliant. However, the EVS scans the SQL files and will mark anything it sees as non-compliant as an error. Hmm. I can see how there is no other way, but just to show how this is throwing the net too wide:

1. I have lots of old SQL scripts dating back years in time. I make a habit of *never* touching old SQL files. I just want to be absolutely 200% sure that regardless of whichever version people are uploading the upgrade will lead to the same SQL Schema. So no touching of these files. But now my module fails with a bunch of "NOT FOR REPLICATION" errors on old scripts (this used to be a standard bit in SQL back in the day).

2. There are *optional* bits to my module. There was also a fail in a script which is used by a debugging tool to measure the size of data tables. If this wouldn't work in Azure, well, no biggie. I just wouldn't have that info during a support request.

My point is: *before* we start handing out badges we need to make sure the procedure does allow for this kind of deviance IMO. This is: unless the script will actually throw an error (#2 above did not throw an error when installed on Azure).

Peter