Hi,

We have a azure database in our lab. But the performance is very slow. But there is no clue to identify my database having problem to returning data like that. All values from azure console like CPU(%), Memory(%) , IO and DTU(%) are very minimal and everything is good(pakka).

How do we know that my database having issues or slow in response. Because our application getting slow response from Azure database. So it created serious issues from our end. Please tell me how to resolve this issue. What is max response time to execute one query?

Regards

Rathidevi

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

• Proposed as answer by Niall Moran - IrelandMicrosoft employee 16 hours 18 minutes ago

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

• Proposed as answer by Niall Moran - IrelandMicrosoft employee 16 hours 29 minutes ago

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

• Proposed as answer by Niall Moran - IrelandMicrosoft employee Thursday, July 16, 2015 2:50 PM

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

• Proposed as answer by Niall Moran - IrelandMicrosoft employee Thursday, July 16, 2015 2:50 PM

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

• Proposed as answer by Niall Moran - IrelandMicrosoft employee Thursday, July 16, 2015 2:50 PM

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

• Proposed as answer by Niall Moran - IrelandMicrosoft employee Thursday, July 16, 2015 2:50 PM
• Marked as answer by Casey KarstMicrosoft employee, Moderator 13 hours 47 minutes ago

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

• Proposed as answer by Niall Moran - IrelandMicrosoft employee Thursday, July 16, 2015 2:50 PM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Tuesday, July 21, 2015 5:21 PM

First off I would suggest you rule out the query. In other words make sure the query you are testing is not badly optimized and performing poorly as DTUs is a measure of server and disk performance and not query.

For example, if you ran this exact database on a dedicated SQL Server would this query perform ok?

If you are sure the query is well optimized and working well then have you tried a different performance level for sql database, e.g. P3.

If your query performance is fine and changing sql tiers doesn't improve performance then there could be something wrong with the network latency.

If this is the case you will need to log a support ticket as they will need to monitor your transactions to see if something is wrong.

You can get more info on sql database performance plans here:

https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx

and log a support ticket here:

http://azure.microsoft.com/en-us/support/options/

Regards

Niall

I hope this helps, if it does please mark the post as the answer.

• Proposed as answer by Niall Moran - IrelandMicrosoft employee Thursday, July 16, 2015 2:50 PM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Tuesday, July 21, 2015 5:21 PM