Ashish Sharma

There are several ways to capture memory dump for your Azure Web App. But retrieving the memory dump using Kudu is really one of the easiest & quickest way to do it. Follow the below steps to capture Memory Dump: Go to your Azure Web App and click on Advanced Tools in left Navigation bar as shown below: It will open a new page https://<<web app name>>.scm.azurewebsites.net. Now open the Process explorer. The W3WP.exe process in the red box is the one running the KUDU site while W3WP.exe process in the green box is the one responding to requests to your Web App. Then, right-click on the W3WP process, in the green box and select Download Memory Dump -> Full Dump, as illustrated below. It will take sometime to capture the dmp file and once it is created, you should get prompted to save the dmp file.

Whenever a database is frequently updated via INSERT, UPDATE, or DELETE statements, over time these modifications can cause the information in the index to become scattered in the database (fragmented). As data is modified in a database, the database and its indexes become fragmented. As indexes become fragmented, ordered data retrieval becomes less efficient and reduces database performance. If database indexes are fragmented, the SQL Server query optimizer may choose a non-optimal execution plan when using an index to resolve a query. Heavily fragmented indexes can degrade query performance and cause your application to respond slowly. The below script helps to provide every index on every table in your database, ordered by percentage of index fragmentation. SELECT dbschemas.[name] as 'Schema', dbtables.[name] as 'Table', dbindexes.[name] as 'Index', indexstats.alloc_unit_type_desc, indexstats.avg_fragmentation_in_percent, indexstats.page_count FROM sys.dm_db_