SQL probe metrics along with associated checks that compare characteristics of the current table with other tables can be important validation steps.
It is possible to write probes that reference other tables in a project. However, since project variables are not accessible the table names must be hard coded rather than using the DSS feature that enables referencing tables via variables (e.g., ${projectKey}_tablename) so that the resolved table names are automatically unique across projects.
Not having this functionality means when projects are copied (e.g., for others on the team to work on) such probes either fail or give misleading results (by referencing a table from a previous project). Or alternatively we don't write such probes even when they would be useful to avoid the extra work of fixing problems and the risk of forgetting to make table name changes.
The request then is to be able use project variables in a SQL probe.
