Hi,

We have a SQL database instance in our lab. we have using STANDARD S0 tier. We have an application which used that SQL database from azure to store the datas. But the data transmission is very very slow from my application to azure database. 

In azure console there is no issues with CPU percentage, Memory utilization, Deadlock and DTU etc which is visible in monitor page of SQL Database. 

I have enabled the audit log for analysis. I can not download the link which is given by azure console. Please help to resolve this.

1) How do we know my azure database is slow.

2) When we execute the query it returns no data, the process still continue..

3) Is there any other way to resolve this problem. 

Thanks & Regards

Rathidevi

Hello Rathidevi,

Thank you for reaching out. When you transfer data into a SQL Database there are three potential points where you could have slowdowns:

1. When reading the data from the source.
2. When the data is transferred to the destination (internet connection).
3. When writing to the SQL Database.

On #3 specifically, checking the DTU utilization of the DB is the first step. Specifically you should check the log write percent. To get the most accurate and recent data, open a second connection to the database and query the view sys.dm_db_resource_stats in the database. If you don't max out the available resources and don't have any locking issues, chances are there the connection to the DB or reading the data from the sources is slow.

Can you please share some more data on your #2? What are you trying to do? What do you mean by the process still continues?

Thanks,

Jan

• Edited by Jan EngelsbergMicrosoft employee 14 hours 18 minutes ago

Hello Rathidevi,

Thank you for reaching out. When you transfer data into a SQL Database there are three potential points where you could have slowdowns:

1. When reading the data from the source.
2. When the data is transferred to the destination (internet connection).
3. When writing to the SQL Database.

On #3 specifically, checking the DTU utilization of the DB is the first step. Specifically you should check the log write percent. To get the most accurate and recent data, open a second connection to the database and query the view sys.dm_db_resource_stats in the database. If you don't max out the available resources and don't have any locking issues, chances are there the connection to the DB or reading the data from the sources is slow.

Can you please share some more data on your #2? What are you trying to do? What do you mean by the process still continues?

Thanks,

Jan

• Edited by Jan EngelsbergMicrosoft employee 14 hours 8 minutes ago

Hello Rathidevi,

Thank you for reaching out. When you transfer data into a SQL Database there are three potential points where you could have slowdowns:

1. When reading the data from the source.
2. When the data is transferred to the destination (internet connection).
3. When writing to the SQL Database.

On #3 specifically, checking the DTU utilization of the DB is the first step. Specifically you should check the log write percent. To get the most accurate and recent data, open a second connection to the database and query the view sys.dm_db_resource_stats in the database. If you don't max out the available resources and don't have any locking issues, chances are there the connection to the DB or reading the data from the sources is slow.

Can you please share some more data on your #2? What are you trying to do? What do you mean by the process still continues?

Thanks,

Jan

• Edited by Jan EngelsbergMicrosoft employee Wednesday, July 15, 2015 5:00 PM

Hello Rathidevi,

Thank you for reaching out. When you transfer data into a SQL Database there are three potential points where you could have slowdowns:

1. When reading the data from the source.
2. When the data is transferred to the destination (internet connection).
3. When writing to the SQL Database.

On #3 specifically, checking the DTU utilization of the DB is the first step. Specifically you should check the log write percent. To get the most accurate and recent data, open a second connection to the database and query the view sys.dm_db_resource_stats in the database. If you don't max out the available resources and don't have any locking issues, chances are there the connection to the DB or reading the data from the sources is slow.

Can you please share some more data on your #2? What are you trying to do? What do you mean by the process still continues?

Thanks,

Jan

• Edited by Jan EngelsbergMicrosoft employee Wednesday, July 15, 2015 5:00 PM

Hello Rathidevi,

Thank you for reaching out. When you transfer data into a SQL Database there are three potential points where you could have slowdowns:

1. When reading the data from the source.
2. When the data is transferred to the destination (internet connection).
3. When writing to the SQL Database.

On #3 specifically, checking the DTU utilization of the DB is the first step. Specifically you should check the log write percent. To get the most accurate and recent data, open a second connection to the database and query the view sys.dm_db_resource_stats in the database. If you don't max out the available resources and don't have any locking issues, chances are there the connection to the DB or reading the data from the sources is slow.

Can you please share some more data on your #2? What are you trying to do? What do you mean by the process still continues?

Thanks,

Jan

• Edited by Jan EngelsbergMicrosoft employee Wednesday, July 15, 2015 5:00 PM

Hello Rathidevi,

Thank you for reaching out. When you transfer data into a SQL Database there are three potential points where you could have slowdowns:

1. When reading the data from the source.
2. When the data is transferred to the destination (internet connection).
3. When writing to the SQL Database.

On #3 specifically, checking the DTU utilization of the DB is the first step. Specifically you should check the log write percent. To get the most accurate and recent data, open a second connection to the database and query the view sys.dm_db_resource_stats in the database. If you don't max out the available resources and don't have any locking issues, chances are there the connection to the DB or reading the data from the sources is slow.

Can you please share some more data on your #2? What are you trying to do? What do you mean by the process still continues?

Thanks,

Jan

• Edited by Jan EngelsbergMicrosoft employee Wednesday, July 15, 2015 5:00 PM

Hello Rathidevi,

Thank you for reaching out. When you transfer data into a SQL Database there are three potential points where you could have slowdowns:

1. When reading the data from the source.
2. When the data is transferred to the destination (internet connection).
3. When writing to the SQL Database.

On #3 specifically, checking the DTU utilization of the DB is the first step. Specifically you should check the log write percent. To get the most accurate and recent data, open a second connection to the database and query the view sys.dm_db_resource_stats in the database. If you don't max out the available resources and don't have any locking issues, chances are there the connection to the DB or reading the data from the sources is slow.

Can you please share some more data on your #2? What are you trying to do? What do you mean by the process still continues?

Thanks,

Jan

• Edited by Jan EngelsbergMicrosoft employee Wednesday, July 15, 2015 5:00 PM

Hello Rathidevi,

Thank you for reaching out. When you transfer data into a SQL Database there are three potential points where you could have slowdowns:

1. When reading the data from the source.
2. When the data is transferred to the destination (internet connection).
3. When writing to the SQL Database.

On #3 specifically, checking the DTU utilization of the DB is the first step. Specifically you should check the log write percent. To get the most accurate and recent data, open a second connection to the database and query the view sys.dm_db_resource_stats in the database. If you don't max out the available resources and don't have any locking issues, chances are there the connection to the DB or reading the data from the sources is slow.

Can you please share some more data on your #2? What are you trying to do? What do you mean by the process still continues?

Thanks,

Jan

• Edited by Jan EngelsbergMicrosoft employee Wednesday, July 15, 2015 5:00 PM