Support for the full length of T-SQL statements that are run in an Azure SQL Data Warehouse
The customer I’m working with is asking if there’s a way to know the full length of T-SQL statements that are run in an Azure SQL Data Warehouse instance.
They are using sys.dmpdwexec_requests, but it truncates the query text keeping 4000 bytes.
We are excited to announce that we have implemented Query Store for Azure SQL Data Warehouse. Query Store enables storing the full query text and aggregated execution statistics for all queries for a period of 7 days. You can learn more about Query Store in our blog post:
Principal Program Manager
Azure SQL Data Warehouse team
Jothi Iyer commented
In addition to the entire query text we also need the system tables big enough to hold atleast 1 week history. Having just one day of history is not cutting it anymore. Hopefully some one looks into this issue also
Filious Louis commented
Can someone provide an ETA for this feature?
Log the entire query text, without how can we troubleshoot
We need this feature implemented on the on-premise APS 2016.
Azure DBA commented
Can't understand how one can troubleshoot a problem query when it is not logged in full. Is it realistic to believe all SQL is written by a person who can be conveniently and quickly reached by phone/IM/e-mail? What do you do when an 3rd-party application is producing the SQL dynamically?