Problem in Azure SQL Database Basic Tier

I have a WinForms Application was using Azure SQL Database (Web)
It was working fine with web version (for last 2.5 years). 
After Microsfot's new offerings of New Tiers of Azure SQL Database, 
I tried Basic Tier.
Observation for last 24 hours according to Azure Portal when Database in
BASIC state :::
Successful Connections : 2 (Max), 1.5(Avg), 3(Total)
Failed Connections : 0 (Max), 0 (Avg), 0 (Total)
Throttled Connections : 0 (Max), 0 (Avg), 0 (Total)
Deadlocks : 0 (Max), 0 (Avg), 0 (Total)
Storage : 23.38MB (Min), 23.75MB (Max), 23.47MB (Avg)
CPU Percentage : 0 (Min), 3.34 (Max), 1.14 (Avg)
Log Writes Percentage : 0 (Min), 0.05 (Max), 0.02 (Avg)
Physical Data Reads Percentage : 0 (Min), 0.01 (Max), 0 (Avg)
The WinForm Application working fine but there is some problem:
When a Report is generated (local .rdlc), the connection gives "Timeout Expired"
This problem occurs only in 25% cases (in 75% cases works fine)with same data.
If I upgrade database to Standard (S1) it works fine.
QUESTION IS :
Resource Stats show it is using very low resources.
like CPU percentage 3.34 (Max), Log Writes Percentage 0.05 (Max)
and Physical Data Reads Percentage 0.01 (Max)
Why the report not works in 25% cases in BASIC state but works in STANDARD S1 state ?
The price of Standard S1 is 8 timeshigher then BASIC
Thanks

Hello Fanny,
Thanks for reply.
I know it and that's why I mentioned different resource stats.
My database (BASIC) using only :
CPU Percentage :  3.34
(Max)
Log Writes Percentage :
0.05 (Max)
Physical Data Reads Percentage :
0.01 (Max)
While Microsoft says if any parameter goes beyond 80% usage then you need to upgrade tier
Please see following video on Channel 9:
Azure SQL Database and the new Database Throughput Unit 
 by Tobias Ternstrom – Principal Program Manager Lead for performance in Azure SQL Database
Thanks

Similar Messages

  • Contained Database Users are now available in Azure SQL Database Update preview

    Contained Database Users should be of particular help for people migrating to Azure SQL Database. At the moment, this is a preview release but you can start testing. Here is the announcement of the
    preview with links to more information.
    New SQL Database public preview with new Standard-tier performance level
    Previously announced in November 2014 and now available for customers to try, the
    new
    public preview of SQL Database improves the compatibility of SQL Server applications for Azure SQL Database. Details of this preview are available on the
    SQL
    Database documentation webpage, including the following key enhancements: easier management of large databases to support heavier workloads with parallel queries
    and online indexing, support for programmability functions like CLR and XML index to support more robust application design, improved monitoring and troubleshooting with XEvents and 100 new Dynamic Management Views (DMV), and more performance in the Premium
    tier.
    To try this preview, please sign up via the Preview
    features webpage. Only SQL Database servers with a mix of one or more Basic, Standard, or Premium (not Web or Business) databases are compatible and eligible to
    upgrade to the preview. Please note that any move of an existing Basic, Standard, or Premium database into this preview is irreversible; we recommend that you create a database copy or leverage test databases on any server enrolled in this preview.
    A new Standard-tier performance level, S3, is also available in this preview which gives you more pricing flexibility between Standard and Premium. S3 will deliver 100 Database Throughput Units (DTU) and all the features available in the Standard tier. Please
    note that S3 will appear on your bill as a multiple of S2 until further notice.
    For more information, please visit the SQL
    Database webpage and the
    Microsoft
    Azure Blog. For a comprehensive look at pricing, please visit the
    SQL
    Database pricing webpage.
    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    Hello Rick
    That is great, one thing I'd like to ask, does it support SSMS,SSDT?
    No sign of that yet, that I’ve seen.....
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • Azure SQL DB Basic Edition Preview: "Session Request Limit Reached" Stuck and Doesn't Clear - SQL DB Bug?

    Edit: I have updated the below to reflect that it took four hours for the database to unblock. This looks like a bug to me. SQL Server seemed to believe there were 30 running sessions with open requests nearly four hours after the client
    side connections were terminated (and thus in the process blocking SQL Server from accepting new connections).
    Problem
    I am running a preview "Basic" edition SQL DB and have hit a problem with Azure SQL DB blocking database access for an extended time period.
    I was running a test, which was running normally for several hours (loading small batches of data), then suddenly lots of connection timeouts (error type 1 below).  My workload was constant over the whole test - but if the server was suddenly under
    pressure, I accept this might happen - no problem with me so far. 
    Upon retrying, the errors then changed to request limit exceeded (error type 2 below).
    I am surprised I hit the limit in the first place, since the test code closes the SQL Connection on a timeout error and reopens.  (In C#, the code is wrapped in a using{} to ensure prompt connection closure).  Still, perhaps the amount of concurrent
    work on the server did momentarily hit this limit.  Perhaps fair enough on this point too.
    BUT:  Surprisingly, nearly four hours later, I was still unable to connect to the database - it was refusing new connections.  Either from my worker role or from the Azure Management Website.  The Management Window, upon trying to connect,
    failed with exactly the same text as error type 2 below.
    Further, sys.resource_stats (from the master db, which is still accessible) is reporting that there were 30 active sessions, 30 active workers (see extract below) for four afters after the test ended.  Even though during this time period the Azure Cloud
    Service that was generating the SQL requests was stopped too (so the client side of any open requests were long since dead).  Also,
    the CPU, Log Write and Phys Data Read columns in sys.resource_stats are all showing 0 for the four hours after the test ended.  This to me suggests a fault condition that isn't clearing server-side.
    Why was the database unavailable for four hours?  Why did Azure believe that there were 30 open requests? (each request was an insert of 1000 rows, each of 400 bytes, i.e. pretty small so no way should they take this long to process).
    PS.  To be clear, none of the above is a complaint.  I completely accept that the service in in preview, different SLA, etc.  I am writing to a) check that I haven't missed anything and b) if this is a bug, to report it.
    Appendix
    Error Type 1
    System.Data.SqlClient.SqlException:  Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    Error Type 2
    SqlException: Resource ID : 1. The request limit for the database is 30 and has been reached. See 'http://go.microsoft.com/fwlink/?LinkId=267637' for assistance.
    Metrics
    The following is an extract from sys.resource_stats for the affected time period.  SQL Server seems to wrongly believe/report that there are 30 pending requests between 6:20 and 10:45.  It thus blocks any further requests during this time.  There
    were NO client connections during this time, either new or previously opened.
    start time
    end time
    sku
    session count
    worker count
    avg cpu
    avg phys data read
    avg log write
    07 Jun 11:15
    07 Jun 11:20
    Basic
      0
    0
    0
    0
    0
    07 Jun 10:50
    07 Jun 10:55
    Basic
      0
    0
    0.5
    0
    0
    07 Jun 10:40
    07 Jun 10:45
    Basic
      30
    30
    0.01
    0
    0
    07 Jun 09:35
    07 Jun 09:40
    Basic
      30
    30
    0.02
    0
    0
    07 Jun 09:20
    07 Jun 09:25
    Basic
      30
    30
    0
    0
    0
    07 Jun 09:10
    07 Jun 09:15
    Basic
      30
    30
    0.01
    0
    0
    07 Jun 08:40
    07 Jun 08:45
    Basic
      30
    30
    0
    0
    0
    07 Jun 08:20
    07 Jun 08:25
    Basic
      30
    30
    0.01
    0
    0
    07 Jun 08:10
    07 Jun 08:15
    Basic
      30
    30
    0.01
    0
    0
    07 Jun 07:55
    07 Jun 08:00
    Basic
      30
    30
    0
    0
    0
    07 Jun 07:25
    07 Jun 07:30
    Basic
      30
    30
    0.01
    0
    0
    07 Jun 07:15
    07 Jun 07:20
    Basic
      30
    30
    0
    0
    0
    07 Jun 07:05
    07 Jun 07:10
    Basic
      30
    30
    0.01
    0
    0
    07 Jun 06:55
    07 Jun 07:00
    Basic
      30
    30
    0
    0
    0
    07 Jun 06:45
    07 Jun 06:50
    Basic
      30
    30
    0.15
    0
    0
    07 Jun 06:20
    07 Jun 06:25
    Basic
      30
    30
    0.01
    0
    0
    07 Jun 06:15
    07 Jun 06:20
    Basic
      30
    30
    0.22
    0
    0
    07 Jun 06:10
    07 Jun 06:15
    Basic
      26
    26
    0.13
    0
    0
    07 Jun 06:05
    07 Jun 06:10
    Basic
      20
    20
    0.14
    0
    0
    07 Jun 06:00
    07 Jun 06:05
    Basic
      13
    13
    0.12
    0
    0
    07 Jun 05:55
    07 Jun 06:00
    Basic
      7
    7
    0.12
    0
    0
    07 Jun 05:50
    07 Jun 05:55
    Basic
      1
    1
    54.04
    0
    93.47
    07 Jun 05:45
    07 Jun 05:50
    Basic
      1
    0
    1.4
    0
    2.06
    07 Jun 05:40
    07 Jun 05:45
    Basic
      1
    1
    55.17
    0
    88.35
    07 Jun 05:35
    07 Jun 05:40
    Basic
      1
    0
    52.05
    0
    90.01
    07 Jun 05:30
    07 Jun 05:35
    Basic
      1
    1
    54.95
    0
    90.1
    07 Jun 05:25
    07 Jun 05:30
    Basic
      1
    1
    56.38
    0
    89.82
    07 Jun 05:20
    07 Jun 05:25
    Basic
      1
    0
    52.15
    0
    90.19
    07 Jun 05:15
    07 Jun 05:20
    Basic
      1
    0
    52.76
    0
    87.86

    Hi Chris,
    Thanks for testing the new Basic edition and for reporting this issue. Without some more investigation it is hard to tell what exactly has happened here.
    To be able to take a closer look I would need some more information from you. Could you please reach out to me via email (firstname DOT lastname AT microsoft DOT com)? I will then let you know what additional information we and will kick-off
    the investigation.
    Thanks,
    Jan

  • Azure SQL Database

    Folks,
    Not sure if this is the right forum to ask these questions, I am planning to sign up for Azure SQL Database and VMs. I am trying answers to following. Any information is appreciated.
    What is the reliability measure of the Azure SQL Database. Is it five 9’s ?
    What is the "MAX Worker Threads” performance measure as mentioned here:
    http://msdn.microsoft.com/en-us/library/azure/dn741336.aspx
    Does “MAX session” correspond to maximum number simultaneous of DB JDBC connections.
    Is it tenant based service where multiple tenants are hosted on the Azure database.
    What is the architecture of Azure SQL database, Is it centralized on a single server or over a cluster of machines ?
    What is the high level architecture of the VMs and SQL DB.
    What is the nature, bandwidth and reliability of connectivity between Azure VMs and Azure SQL DB.
    Is this network capacity between VMs and SQL DB shared between multiple tenants.
    How are the SLAs guaranteed (ensured) and throttled/enforced (to curb over-utilization).
    If we horizontly scale Azure VMs to twice number of current VMs, will the temporal locality of the new VMs has lower network performance in terms of latency or bandwidth than the existing VMs.
    Are there any per Azure VM limits on access to Azure SQL DB.
    If for some reason SQL DB crashes experiences, Is the Data recoverable.
    Can the Azure SQL DB be backed up in Azure Cloud/ or Amazon S3
    Thanks,
    Ajay

    Hi Ajay,
    These msdn forums are the actually the best place to ask questions. 
    I guess you have some scenario in back of your mind that makes you ask these questions, if you can share that with us we may better answer your questions instead of giving you information that may not be most usable for you, regardless here it goes.
    I will do my best to answer all your questions
    What is the reliability measure of the Azure SQL Database. Is it five 9’s ?
    VS: It's 4 nines (99.99) The 99.99% uptime SLA applies to Basic, Standard, and Premium service tiers only. 
    SQL Database Web and Business Editions have an established uptime SLA of 99.9%.
    http://azure.microsoft.com/en-us/services/sql-database/
    What is the "MAX Worker Threads” performance measure as mentioned here:
    http://msdn.microsoft.com/en-us/library/azure/dn741336.aspx
    VS: SQL Database governs the limit on the number of concurrent worker threads (requests) to a database. 
    Any database with more than the allowed limit of concurrent requests will receive error 10928, and further requests on this database can be denied.
    http://msdn.microsoft.com/en-us/library/azure/dn338078.aspx
    Does “MAX session” correspond to maximum number simultaneous of DB JDBC connections.
    VS: Yes, SQL Database governs the limit on the number of concurrent sessions that can be established to a database. When concurrent session limit for a database is reached, new connections to the database are denied and user will receive error
    code 10928. However, the existing sessions to the database are not terminated.
    http://msdn.microsoft.com/en-us/library/azure/dn338078.aspx
    Is it tenant based service where multiple tenants are hosted on the Azure database.
    VS: Yes and No, Yes because its offered as SAAS, yes multiple tenants are hosted on Azure DB, but they are isolated and also depends on the tier you choose. SQL Azure is designed for Massive scaling, so if you were worried about slowness due
    to multi tenant hosting, trust me that should last thing to be worried about.
    No, because you can choose to go all the way to premium (now that does not mean you are the only db on the server but its super high performing database out there)
    What is the architecture of Azure SQL database, Is it centralized on a single server or over a cluster of machines ?
    VS: Its hosted in Microsoft Datacenters and offered as a service, although we can go in detail of architecture of SQL Azure but for this set of questions its irrelevant. Performance is massive on SQL Azure, it can be scaled out or scaled down
    on demand.
    What is the high level architecture of the VMs and SQL DB.
    VS: Not following your question here, what is meant by architecture of VM?
    What is the nature, bandwidth and reliability of connectivity between Azure VMs and Azure SQL DB.
    VS: The connectivity in general is great unless you decide to host one service in part of the world and other totally other corner, in that case also I have seen good connectivity between the two given normal latency.
    Is this network capacity between VMs and SQL DB shared between multiple tenants.
    VS: Not following your question in entirty, do you mean network capacity in terms of GB/Sec? if your vm and sql are in same Data Center its the fastest connectivity you can get out there in market on any cloud or for that matter on prem :)
    they apparantely have a faster network in their DC than many giant companies have on prem.
    How are the SLAs guaranteed (ensured) and throttled/enforced (to curb over-utilization).
    VS: MS have protection against many threats, DOS being one of them, Microsoft has done the best job among all the cloud providers out there to inform thier customers about outages, in a recent summit this was also discussed in detail and suggestions
    were made to improve on the portal feature.
    Each time an service goes down its reported on the portal on service health page, they are improving on the SLA breach report, at this moment its part of your invoice. I have personally not seen a single breach on my services, I am actively using Azure for
    last 5+ years.
    If we horizontly scale Azure VMs to twice number of current VMs, will the temporal locality of the new VMs has lower network performance in terms of latency or bandwidth than the existing VMs.
    VS: number of VMs have nothing to do with network performance, keep in mind the fabric underneath is build for massive scale, network performance and latency will vary (they keep improving) if you choose to create your VMs in a different DCs
    then you would come across some latency and that's normal. 
    Are there any per Azure VM limits on access to Azure SQL DB.
    VS: these are not per VM limits, they are driven by MAx_THREAD and MAX_SESSION, please refer to the link above in the question for Max worker thread
    If for some reason SQL DB crashes experiences, Is the Data recoverable.
    VS: I would be careful to answer this, if you choose to use SQL Azure (which is offered as SAAS) then yes MS takes care of data replication to ensure SLA. if you choose to host your own SQL DB on your VM in Azure, MS is not responsible for
    the data recovery, you will have to take care of it (because now you are not talking about PAAS, instead you are going for IAAS)
    Can the Azure SQL DB be backed up in Azure Cloud/ or Amazon S3
    VS: Ofcourse, I am not very familiar with Amazon S3 but i see no reason why it can't be done.
    hope this helps
    Please mark as answered if it helped
    Vishal Narayan Saxena http://twitter.com/vishalishere http://www.ogleogle.com/vishal/

  • Concerns over switching between new Azure SQL Database Service Tiers

    Windows Azure's new SQL Database
    service tier pricing model will be put into effect in less than 12 months. We currently have SQL Databases on the Business and Web Edition pricing models.
    We recently asked Azure Support a number of questions around the scalability and ability to switch between these tiers. The responses so far have been far from encouraging:
    Q: If we exceed the criteria for a given tier (see http://msdn.microsoft.com/library/azure/dn741336.aspx), how will Azure respond? For example, if we are on the S1 service tier, and we exceed the maximum number of sessions (200), will any new sessions be
    blocked until we manually increase the service tier? Or will you automatically move (and bill) us to/for the next tier level?
    A: If you exceed the criteria of the existing tier, you shall be notified of performance issue like throttling. Users may experience slowness and blocking. There will not be any automatic upgrade.
    Q: So to confirm, if we suddenly experience increased, unanticipated client activity overnight due to our web site becoming more popular, you will be blocking any user sessions over and above our performance level limit, until we manually make the transition
    to the next level? Is there no “overdraft” facility/scalability in this respect? If this scenario took place within a short space of time, how would we have time to react? Simply blocking new sessions and preventing customers from using our site is not acceptable.
    A: I’m sure you understand that SQL Azure database is a shared resource and hence we cap the resources for individual subscription so that a fair service is provided to all the concurrent users. If you feel that you cannot compromise on the user experience
    then you shall think of an edition that best suits you. Please refer to the following document to best understand the throttling and its impact. http://social.technet.microsoft.com/wiki/contents/articles/1541.windows-azure-sql-database-connection-management.aspx#Throttling_Limits
    Q: Since the changing of the performance level could take several minutes/hours depending on the size of the database, would we experience any downtime/degradation of performance of the database during this period?
    A: You might
    Q: If downtime/degradation of performance are a possibility whilst we switch service tiers, what do Microsoft recommend we do to safeguard against this? Should we create a second database on a higher tier level and then export the data from the lower tier and
    import to the higher, before switching over? How do Microsoft recommend we switch tiers in a production environment with minimal disruption?
    A: If you want to upgrade the tiers due to degradation of performance, you will have to create another database on a higher tier and import the data.
    One of our key reasons for moving to Azure hosting was the seamless scalability it appeared to offered. As you can imagine, the responses above are a major concern for our production environment. Does anyone else have any thoughts or concerns in this respect?

    James,
    I reviewed the support incident you referred to and believe that the questions you asked may have been answered later in the interaction you had with the engineer.  For the benefit of others viewing this forum I want to reiterate the answers
    to your key questions here as well.
    Q. What is the behavior when you reach the limits for the service tier?
    A. Each service tier currently has limits on 4 different dimensions (CPU, physical reads, log writes and memory) of resource consumption.  When you reach one of the limits, the behavior depends on which resource limit you are hitting, but
    generally speaking is consistent with the behavior you would see with a similar hardware limit in the SQL Server box product.  For example, when you reach the CPU limit your queries will start showing more SOS_SCHEDULER_YIELD waits,
    the memory limit will cause a higher percentage of pages to be read from disk instead of the buffer cache (PAGEIOLATCH_xx waits), etc.  This set of limits does not directly abort any of your queries--they just run longer as they
    vie for the fixed set of resources made available to your database.  In a system where the load greatly exceeds the resources, queries may start to time out.
    The new service tiers continue with the Web/Business edition behavior of limiting the number of sessions and concurrent requests (worker threads) you can have.  When you exceed these limits you'll get error 10928.  Note that
    each tier in Basic/Standard/Premium have different values for these limits (http://msdn.microsoft.com/en-us/library/azure/dn369873.aspx) than Web/Business and thus may encounter the errors at different usage levels.  The key is choosing the appropriate
    service level for the application, and to facilitate that the sys.resource_stats view shows historical usage information so you know where you stand as far as reaching any of the limits.  This resource consumption data is also available in the portal.
    Q. Is it possible to switch service tiers, and is there any disruption when you do so?
    A. Yes, you can change between service tiers as described in this MSDN documentation (http://msdn.microsoft.com/en-us/library/azure/dn369872.aspx).  This can be done through the portal, powershell, or REST APIs.  [The preview currently has a restriction
    where legacy servers don't support switching to Basic/Standard which is expected to be removed in the near future.]  The link above outlines the limits on the number of tier changes you can do in a 24 hour period, expected time to perform the change, and
    the client disconnect that occurs.
    If you have further questions, feel free to re-engage on the support incident or reply to this forum thread.

  • Can No Longer Connect to Azure SQL Databases

    As of this morning, I am no longer to connect to any of my Azure SQL databases by any (apparent) means. I checked the configuration in the azure portal and my IP address is listed as an allowed IP, however:
    I am unable to connect via SQL Server Management Studio
    My request times out when attempting to visit https://{server_name}.database.windows.net
    What might have caused this?

    Hi ,
    Thanks for posting here.
    To resolve the issue you can try the following steps (in that order):
                    Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port
    (1433) and the fully qualified server name.                
    Note You can follow these steps to obtain the connection string from the Azure Management Portal:                  
                          Log on to the
    Azure Management Portal.                    
                          In the left navigation pane, click
    SQL Databases.                    
                          Select your Azure SQL Database server.                    
                          Click
    Dashboard.                    
                          On the right side, go to the
    quick glance section, and then click Show connection strings.                    
                    Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
    Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).              
                    Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this,
    see
    Azure SQL Database connectivity troubleshooting guide and
    Troubleshooting SQL Server connectivity issues.                
    Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.                
                    Try increasing the connection
    timeout. Microsoft recommends using a connection timeout of at least 30 seconds.              
                    As a best practice ensure retry logic is in place. For more information about the retry logic, see
    Azure SQL Database best practices to prevent request denials or connection termination.              
                  If the previous steps do not resolve your problem, follow these steps to collect more data and contact support:              
                      If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing
    ID.
    Microsoft Customer Support Services can use this information.                
                      For more information about how to enable the logging, see
    how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
    Azure SQL Database Development Considerations.
    Please write back with the exact Error message/ Error Code if this doesn't help.
    Regards,
    Shirisha Paderu.

  • Cannot Connect to Azure SQL Database in Visual Studio 2013

    Beyond Frustrated here.
    I am trying to connect to an Azure SQL database - it has been created, has tables etc. I am trying to create a new Data Connection from within Visual Studio 2013, latest release for VS and Azure. I continue to receive the following error:
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
    (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
    I have ensured that TCP is allowed and above Named Pipes in the Configuration Manager. The associated IP address is allowed on Azure Firewall. Certificate has been added to VS etc. But still no connection. I can see the database in the Azure section in Server
    Explorer, but cannot add a Data Connection. What is equally as frustrating is I have a MacBook Pro running Win 7 sitting right next to my office computer and it can access Azure fine, not problems.
    If anyone has any other ideas on how I might be able to solve this I would love to hear them. Thanks in advance.
    Jeff

    Hi,
     The Error message "   A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is
    configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53) "
    The issue comes up mainly because the application is not able to connect to the server.
    To resolve this issue, try the following steps (in that order):
     Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
    Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).              
     2.  Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port (1433) and the fully qualified server name.                
    Note You can follow these steps to obtain the connection string from the Azure Management Portal:                  
                          Log on to the
    Azure Management Portal.                    
                          In the left navigation pane, click
    SQL Databases.                    
                          Select your Azure SQL Database server.                    
                          Click
    Dashboard.                    
                          On the right side, go to the
    quick glance section, and then click Show connection strings.                    
    Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this, see
    Azure SQL Database connectivity troubleshooting guide and
    Troubleshooting SQL Server connectivity issues.                
    Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.                
    Try increasing the connection timeout. Microsoft recommends using a connection timeout of at least 30 seconds.              
    As a best practice ensure retry logic is in place. For more information about the retry logic, see
    Azure SQL Database best practices to prevent request denials or connection termination.              
          If these  steps do not resolve your problem, follow the below steps to collect more data and contact support:              
       If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing ID.
    Microsoft Customer Support Services can use this information.                   
       For more information about how to enable the logging, see
    how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
    Azure SQL Database Development Considerations.                
      Check out
    the list of best practices for Connecting to Windows Azure SQL Database.
    Regards,
    Shirisha Paderu.

  • Consistently getting "The wait operation timed out" when connecting to Azure SQL Database from a virtual instance...

    I have a web app that is backed by a an Azure SQL Database. The problem is that I had multiple issues when connecting to the database mainly when trying to establish a connection, or timeouts. This is the log I just encountered when trying to use the web
    app.
    [Win32Exception (0x80004005): The wait operation timed out]
    [SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21970; handshake=1; ]
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +671
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +116
    System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1012
    System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +6712291
    System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +152
    System.Data.SqlClient.SqlConnection.Open() +229
    System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +102

    Hi Affar2k,
    According to your description, we need to verify if there is no network issue and the Sqlclient version is older than .NET 4.5.  You can try to connect to the Windows Azure SQL database via SSMS and check if it can run well. When you
    connect to the SQL Azure database via ADO.NET, you need to verify that the server name and passwords are right in the connection string.
    For more information, you can review the following article about how to connect to Windows Azure SQL Database using ADO.NET.
    http://msdn.microsoft.com/en-us/library/windowsazure/ee336243.aspx
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Yesterday I was able to connect Azure SQL Database - Today I am not

    Hello Everyone,
    I have problem with establishing connection with Azure SQL Database. I have read many articles here, tried some solutions but none worked.
    0. On last Friday everything worked well - today it does not.
    1. I added my public IP Address in Azure Management Portal earlier.
    2. I tried different types of login-ways: login@nameserver, I used numeric addresses instead of server names, I set TCP connection manually, added encryption in one case either, tried do establish connection with particular database
    3. Firewall does not block 1433 out connection
    4. My IP address is static
    5. I have no error message displayed using Microsoft SQL Server Management Studio - it just hangs.. - no response at all
    6. I cannot ping the machine but its name is resolved correctly - maybe it does not respond using echo reply on purpose
    7. Status of my database is Active - I am able to connect it and manage via browser and management portal at the moment
    8. When I am trying to connect database via Visual Studio - it hangs.. - VS must be stopped manually via task manager
    9. My local CloudService has problem with connection to the db either
    10. Currently I am not able to deploy my CloudService because when I am trying to Publish it - VS hangs as soon as first Publish dialog window appears. Looks that I am able to deploy cloud service via Management portal only.
    I am still trying to dive into the problem but at this moment I would be grateful for any clues.
    Regards,

    Hi Mekh, hi everyone
    PROBLEM SOLVED.
    Yestarday I updated Azure Firewall rule and database-level firewall rules (master, my_database). I added special input / output protocols (IP, TCP, UDP) rules to my COMODO firewall (MSSMS could send anything and receive anything using IP, TCP and UDP). Status
    of my computer -> database connection was set to ESTABLISHED in netstat output but MSSMS was still unavailable (no response at all - no error message).
    I DECIDED TO UNINSTALL COMODO AT ALL and then if it does not work - reinstall local SQL Server, MSSMS and finally Visual Studio. When Comodo was gone - problem was gone either. Now I have connection with my database using MSSMS and I do not have to reinstall
    anything more.
    Regards,

  • Best Way to Replicate Azure SQL Databases to Lower Environments

    I have XML files delivered to my server where they are parsed into reference data and written to a database (Premium tier).  I want to have that database sync to other databases (Basic tier) so that my non-production environments can use the same reference
    data.
    I tried Data Sync and it seems incredibly slow.  Is Azure Data Sync the best way?  What are my other options?  I don't really want to change my parser to write to 3 different databases each time they receive an updated XML file, but I suppose
    that is an option.

    Greg,
    Data sync is one of the option but I wouldn't recommend as Data-Sync Service is going to be deprecated in near future. I would urge you to go through the options around Geo-replication. There are 3 versions of Geo-repl and i believe Active-Geo replication
    would suit your requirement however the copy of the database which is in sync will also have to be in the same service tier (Basic is not possible). With the current Azure offering, it is not possible to have a sync copy of database with different SLOs. I
    would also recommend you to open a support incident with Microsoft to understand different options of Geo-replication. Throughout the time I was composing my answer, keeping DR (disaster recovery) in mind. If i am mistaken, please let me know.
    -Karthik Krishnamurthy (SQK Azure KKB)

  • Database Initialiser does not create azure sql database

    I have a WPF application In the OnStartup in the app.cs I set the Database initializer and forced the context the initialise my database:
    Debug.WriteLine("Setting Initializer");
    Database.SetInitializer<MyContext>(new MyDatabaseInitializer());
    Debug.WriteLine("Declaring new context");
    using (MyContext c = new MyContext("MyContext"))
    Debug.WriteLine("Force the initialization");
    c.Database.Initialize(true);
    Debug.WriteLine("Done!");
    I created a sql database in the management portal of the azure.
    Copied the connectionstring it provided for ADO.net.
    But my database is not created.
    I also added a firewall rule but nothing happens. I Have no clue what to do.
    Can anybody please help me with this?
    If you need more information please ask i really have to get this sorted out.
    Thanks in advance!

    Hi Turkstra,
    I have tried to use EF to create Azure SQL database, it works as expect, the database 'jambordbcreate' appear in my SQL Azure, below is the detailed codes.
    using System;
    using System.Collections.Generic;
    using System.Data.Entity;
    using System.Linq;
    using System.Text;
    using System.Threading.Tasks;
    namespace CodeFirst
    class Program
    static void Main(string[] args)
    Database.SetInitializer(
    new CreateDatabaseIfNotExists<SchContext>());
    using (var db = new SchContext("Server=tcp:****.database.windows.net,1433;Database=jambordbcreate;User ID=vote@***;Password=***;Trusted_Connection=False;Encrypt=True;Connection Timeout=30"))
    string name = "jambor";
    var student=new Student(){Name=name, ID="1a"};
    db.Students.Add(student);
    db.SaveChanges();
    db.Database.Initialize(true);
    public class Student
    public string ID { get; set; }
    public string Name { get; set; }
    public string age { get; set; }
    public string sex { get; set; }
    public class School
    public string ID { get; set; }
    public string Name { get; set; }
    public virtual List<Student> Students { get; set; }
    public class SchContext : DbContext
    public SchContext(string connection):base(connection)
    public DbSet<Student> Students { get; set; }
    public DbSet<School> Schools { get; set; }
    I suggest  you check your SQL connection, after run your code, please refresh azure portal to see whether your database is exist. Hope this give you some help.
    Best Regards,
    Jambor
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Which is better for performance Azure SQL Database or SQL Server in Azure VM?

    Hi,
    We are building an ASP.NET app that will be running on Microsoft Cloud which I think is the new name for Windows Azure. We're expecting this app to have many simultaneous users and want to make sure that we provide excellent performance to end users.
    Here are our main concerns/desires:
    Performance is paramount. Fast response times are very very important
    We want to have as little to do with platform maintenance as possible e.g. managing OS or SQL Server updates, etc.
    We are trying to use "out-of-the-box" standard features.
    With that said, which option would give us the best possible database performance: a SQL Server instance running in a VM on Azure or SQL Server Database as a fully managed service?
    Thanks, Sam

    hello,
    SQL Database using shared resources on the Microsft data centre. Microsoft balance the resource usage of SQL Database so that no one application continuously dominates any resource.You can try the 
    Premium Preview
    for Windows Azure SQL Database which offers better performance by guaranteeing a fixed amount of dedicated resources for a database.
    If you using SQL Server instance running in a VM, you control the operating system and database configuration. And the
    performance of the database depends on many factors such as the size of a virtual machine, and the configuration of the data disks.
    Reference:
    Choosing between SQL Server in Windows Azure VM & Windows Azure SQL Database
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here. 
    Fanny Liu
    TechNet Community Support

  • Connecting to Azure SQL database in Access 2010

    I've recently purchased a new computer and I had an OBDC connection set up to link to a sql database in azure through access. I am trying to set it up on my new computer but I'm unable to define the specific database. I'm able to make the connection but
    it only allows me into the master database. I've added my IP address in the configure servers but still can't get things to work. Any help would be greatly appreciated.
    thanks
    Lynn

    Hi,
    The following guidelines apply to SQL Database connections using ODBC:
    • When using SQL Server Native Client from SQL Server 2008 R2 or SQL Server 2008, the connection string must include the server name as part of the user name (user@server).
    • You must use TCP/IP as the protocol when connecting to an Azure SQL Database.
    • You cannot create a table in the master database, so therefore you must create a user database to create a table.
    • You cannot execute a use database command to switch to your user database. You must disconnect and connect directly to the user database.
    • You must have a primary key or clustered index on your table to be able to insert data.
    Ref:
    https://msdn.microsoft.com/en-us/library/azure/hh974312.aspx?f=255&MSPPError=-2147217396
    http://blogs.office.com/2010/06/07/access-2010-and-sql-azure/
    https://support.microsoft.com/en-us/kb/2028911/
    Hope this helps you.
    Girish Prajwal

  • Deleting old data won't reduce Windows Azure SQL Database usage

    My Windows Azure SQL Database usage keeps increasing. Deleting old data didn't help much. I was wondering how to figure out the distribution of the usage. All tables in my DB should not occupy more than 5GB and now it is most 12GB. Please help!
    http://yanflex.com

    Hello,
    The database fee is amortized over the month and charged daily. The daily fee depends on the peak size that each database reached that day and the maximum number of databases you use. So, if the peak size of database is 12 GB  and then you delete data
    to reduce the size, it still charge based on 12GB this day.
    You can use the following statement to get the database size:
    SELECT SUM(reserved_page_count)*8.0/1024 as DBsizeinMB
    FROM sys.dm_db_partition_stats;
    Reference:Accounts and Billing in Windows Azure SQL Database
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here.
    Fanny Liu
    TechNet Community Support

  • Running Azure SQL database and reporting services native mode?

    I would like to stand-up a remote Azure SQL Server to do Master Data Services (MDS) and SSRS in native mode. Can this be done from one Azure SQL Server instance?
    William H. Neville Jr.

    Hello,
    Master Data Services (MDS)not supported by Microsoft Azure SQL Database.
    In order to meet your requirement, you can try to create a SQL Server virtual machine in Azure, it similar to on-premises SQL Server installed on VM. It also install the SSRS and you can try to configure the SSRS in native mode.
    To run Master Data Services in a virtual machine in Azure, you should also install the Web Server (Internet Information Services) and Silverlight, and also configure Master Data Services by using Master Data Services Configuration Tool (MDSConfigTool.exe).
    Reference:
    Reporting Services Native Mode Configuration
    Getting Started with SQL Server in Azure Virtual Machines
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here. 
    Fanny Liu
    TechNet Community Support

Maybe you are looking for