SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Windows Azure SQL Database (WASD) Troubleshooting

dorjan avatar
dorjan
26 diapositives · 441 Views · Jul 10, 2014

Windows Azure SQL Database (WASD) Troubleshooting. I will assume basic SQL Server knowledge. Bob Ward Principal Architect Escalation Engineer bobward@microsoft.com. My Goals for You Today. What Will We Cover Today. The Azure Troubleshooting Challenge. WASD is a platform service (PAAS)

Windows Azure SQL Database (WASD) Troubleshooting - slide 1
01 / 26Windows Azure SQL Database (WASD) Troubleshooting
1 / 17

Télécharger la présentation

Windows Azure SQL Database (WASD) Troubleshooting
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Windows Azure SQL Database (WASD) Troubleshooting I will assume basic SQL Server knowledge Bob Ward Principal Architect Escalation Engineer bobward@microsoft.com

  2. My Goals for You Today

  3. What Will We Cover Today

  4. The Azure Troubleshooting Challenge • WASD is a platform service (PAAS) • This is not a VM running SQL Server “box” (IAAS) • Multi-tenant platform • You are sharing a SQL instance with other databases from other customers • You are abstracted from the SQL Server instance, Windows, and computer server • Less admin tasks means lower TCO but also means less access • You are isolated to a specific database • You have a logical server and a master but most things are done in your database • Most things are database scoped (Ex. DMVs) • We make decisions to maximize all database availability • Application design may be required • The service can be updated far quicker than the “box” product

  5. Use min 30sec login timeout WASD Connectivity Errors

  6. Network latency Example Connectivity Errors Be sure to give this to support 40XXX errors unique to WASD May see this after deleting a server After getting dropped on idle connection

  7. Troubleshooting Connectivity History tables – not real time

  8. Demo Tools for Connectivity

  9. WASD Errors full list here These can result in connection termination and possible future rejection of work

  10. The partition is in transition and transactions are being terminated. SHUTDOWN is in progress. Failover

  11. Governance • Max number of concurrent worker threads (currently 180) per database • Msg 10928 if you exceed the limit • Connection terminated. Retry when your concurrent work subsides • Check for blocking problems or inefficient queries • Msg 10929 if the overall system has too many workers • You may get less than 180 max • Connection terminated. You can retry but it may take longer to stabilize • Still could be an application issue but a service issue could also be occurring Resource ID : 1 = worker threads

  12. Quotas • Quota errors for space used • Msg 40544 when you run out of space for your max size for your db • Only reads and DELETE/DROP allowed until you free up space • Use sys.dm_db_partition_stats to find what is consuming space • Solutions • Increase max size • Delete data or drop tables/indexes • Partition out database • But…freeing up may not be immediately recognized Changing MAXSIZE disconnects all users

  13. Throttling Limits Rebuild index Online

  14. Engine Throttling • This is more of a legacy monitoring method used to keep instances healthy • Another external service monitors the health of the instance and computer • Soft throttling – we have detected a resource issue so pick specific databases • Hard throttling – entire instance at risk so all databases are affected • How it Works • Existing requests run to completion • New requests for existing connections and new connections may get Msg 40501 and connection terminated depending on type of request • Reason code in Error has more details on soft vs hard, what will be rejected, and why • throttling in sys.event_log 0x8003 x03 = RejectAll x80 = Hard Throttling on I/O Decode reason codes Another resource

  15. “Not Supported” Errors • USE <db> not supported – specify when connecting • ALTER DATABASE supported minimally (Ex. Name, Edition, MAXSIZE, READ_ONLY) • All DBCC commands not supported except for DBCC SHOW_STATISTICS • Database scoped DMVs supported • Feature Support for Windows Azure SQL Database • Unsupported Transact-SQL Statements (Windows Azure SQL Database) • Partially Supported Transact-SQL Statements (Windows Azure SQL Database)

  16. Demo Using Event Tables to Troubleshoot WASD Errors

  17. WASD and Query Performance

  18. WASD Performance Scenarios

  19. Dynamic Management Views (DMV) for Performance

  20. A look at WASD Wait Types

  21. Demo Troubleshooting Query Performance on WASD

  22. Watch Out for These

  23. Before you contact support • We can do RCA but…. • It can take some time and we may • not have enough history

  24. References • Retry Logic for Transient Failures in Windows Azure SQL Database • Error Messages (Windows Azure SQL Database) • Windows Azure SQL Database Performance and Elasticity Guide • Windows Azure SQL Database Connection Management • sys.event_log documentation • CSS SQL Escalation Blog • Troubleshoot and Optimize Queries with Windows Azure SQL Database

  25. Questions? http://sdrv.ms/Zqdkex Thank you!

  26. The Troubleshooting Checklist • Does the Windows Azure Portal work and list your databases? • Is there a dashboard posting for an outage in your region? • Does the SQL Management Portal work? • Does SQL Server Management Studio work? • Is there an internet provider issue? • Is your firewall configuration correct? • Is the problem Windows Azure vs WASD? • Is there blocking? • Are your queries and index tuned? • Is this really an application retry issue? • Governance, quotas, limits, and throttling are “part of this platform” • Have you looked at Event Tables?