The use of custom SQL queries can lead to inadvertent or unauthorized modifications to your data/database structure. Therefore, make sure that you follow best practices and implement the appropriate end-user read/write privileges at the database level.
Various SQL extensions can require a special character as the variable's first character. For instance, this can be the "at" sign (@) for Transact-SQL or the colon (:) for PL/SQL. Insert the required character before the parameter name within the custom SQL query.
After you specified the SQL query, click Next. On the next page, you can add query parameters and specify its settings.
Validation of Custom SQL Queries
By default, the Query Editor allows you to use only SELECT statements in the query. If necessary, you can disable query validation and allow end-users to include not only SELECT statements into SQL queries. This capability is controlled by the static SqlDataSource.DisableCustomQueryValidation property exposed by the DashboardSqlDataSource class. The Dashboard Designer also allows you to manage validation of custom SQL queries by handling the DashboardDesigner.ValidateCustomSqlQuery event which allows you to specify your own query validation logic.
To manage the validation of custom SQL queries in the Dashboard Viewers, use the following events.