Restricted commands in SQL Mode
Because we believe in our purpose, and our mission to JOIN people ON data, we place a high level of importance on data integrity. To ensure the integrity of your data and datasources, and the data contained in them, Chartio will prohibit the use of the certain commands in SQL Mode to prevent certain use of your data.
Even though many security precautions like these restricted commands are put into place, we still recommend only connecting with a user that is granted read-only access to your database.
We recommend as a best practice to only connect chartio to a replica of a main datasource and not a production database, data warehouse, or data lake.
When Chartio is set up with a read-only access user, members of your organization in Chartio with Edit or Admin access to your database can read the data, but cannot do anything to modify the database.
With this extra level of precaution, Chartio scans and rejects any malicious keywords such as DELETE and INSERT before executing queries.
Additional words we will not allow to be sent to your database in a query from Chartio include:
- add
- alter
- attach
- begin
- break
- catch
- change
- checkpoint
- close
- commit
- continue
- conversation
- copy
- create
- cursor
- dbcc
- deallocate
- declare
- delete
- deny
- disable
- drop
- enable
- end
- execute
- fetch
- grant
- get_transmission_stat
- go
- goto
- insert
- install
- kill
- load
- load_extension
- merge
- notify
- open
- pragma
- purge
- raiserror
- refresh
- rename
- reassign
- receive
- reindex
- release
- replace
- reset
- return
- revert
- revoke
- rollback
- save
- savepoint
- send
- setuser
- show
- shutdown
- start
- stop
- shutdown
- throw
- timer
- truncate
- try
- update
- updatetext
- uninstall
- vacuum
- waitfor
- writetext
- while
We want you to trust the insights you are gaining from the data you are querying in Chartio. We take extra measures to protect your data integrity to give you confidence in the data you are analyzing.