Hi Guyz,

We are in the process of migrating to SQL Azure v12 (PAAS) from on-premise DB. While testing that we have identified lot of queries performance is affected badly and i want to trace those queries. Though i am using DMVs for now but the results are not as helpful as of SQL Profiler. What are the other available options for tracing queries in SQL Azure?

Secondly the queries whose performance got affected are mainly "UPDATE" queries. We didn't observe any issue with them in on-premise DB. Do we have to make any special tweaks to query/database in SQL Azure?

Hello,

You should try out the Query Store feature which captures the history of queries, plans, and runtime statistics, and retains these for your review.
Have a look at this blog post: http://azure.microsoft.com/en-us/blog/query-store-a-flight-data-recorder-for-your-database/ and at the MSDN docs: https://msdn.microsoft.com/en-us/library/dn817826(v=sql.130).aspx

Hope it helps,

Maja

For now you need to rely on DMVs majorly. Just try this : https://azure.microsoft.com/en-us/blog/query-store-a-flight-data-recorder-for-your-database/ and see if helps.

Hello,

You should try out the Query Store feature which captures the history of queries, plans, and runtime statistics, and retains these for your review.
Have a look at this blog post: http://azure.microsoft.com/en-us/blog/query-store-a-flight-data-recorder-for-your-database/ and at the MSDN docs: https://msdn.microsoft.com/en-us/library/dn817826(v=sql.130).aspx

Hope it helps,

Maja

• Proposed as answer by Maja SarenacMicrosoft contingent staff 23 hours 13 minutes ago
• Marked as answer by Suman85 22 hours 4 minutes ago

Hello,

You should try out the Query Store feature which captures the history of queries, plans, and runtime statistics, and retains these for your review.
Have a look at this blog post: http://azure.microsoft.com/en-us/blog/query-store-a-flight-data-recorder-for-your-database/ and at the MSDN docs: https://msdn.microsoft.com/en-us/library/dn817826(v=sql.130).aspx

Hope it helps,

Maja

• Proposed as answer by Maja SarenacMicrosoft contingent staff 23 hours 24 minutes ago
• Marked as answer by Suman85 22 hours 16 minutes ago

Hello,

You should try out the Query Store feature which captures the history of queries, plans, and runtime statistics, and retains these for your review.
Have a look at this blog post: http://azure.microsoft.com/en-us/blog/query-store-a-flight-data-recorder-for-your-database/ and at the MSDN docs: https://msdn.microsoft.com/en-us/library/dn817826(v=sql.130).aspx

Hope it helps,

Maja

• Proposed as answer by Maja SarenacMicrosoft contingent staff Wednesday, September 02, 2015 7:56 AM
• Marked as answer by Suman85 Wednesday, September 02, 2015 9:04 AM

Hello,

You should try out the Query Store feature which captures the history of queries, plans, and runtime statistics, and retains these for your review.
Have a look at this blog post: http://azure.microsoft.com/en-us/blog/query-store-a-flight-data-recorder-for-your-database/ and at the MSDN docs: https://msdn.microsoft.com/en-us/library/dn817826(v=sql.130).aspx

Hope it helps,

Maja

• Proposed as answer by Maja SarenacMicrosoft contingent staff Wednesday, September 02, 2015 7:56 AM
• Marked as answer by Suman85 Wednesday, September 02, 2015 9:04 AM

Hello,

You should try out the Query Store feature which captures the history of queries, plans, and runtime statistics, and retains these for your review.
Have a look at this blog post: http://azure.microsoft.com/en-us/blog/query-store-a-flight-data-recorder-for-your-database/ and at the MSDN docs: https://msdn.microsoft.com/en-us/library/dn817826(v=sql.130).aspx

Hope it helps,

Maja

• Proposed as answer by Maja SarenacMicrosoft contingent staff Wednesday, September 02, 2015 7:56 AM
• Marked as answer by Suman85 Wednesday, September 02, 2015 9:04 AM

Thanks a ton Maja :)

Thanks Harsh & Maja for providing such a useful tool.

Using this tool I have identified that "Clustered Index Update" is taking huge time. As we know that the prerequisite of SQL Azure is every table should have a Clustered Index. So i can't remove the clustered index even if I want. But is there any better way to reduce this operation cost?