Warning: Constant WP_TEMP_DIR already defined in /var/www/html/blogs/joe/wp-config.php on line 93
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
{"id":1180,"date":"2014-04-08T07:04:30","date_gmt":"2014-04-08T14:04:30","guid":{"rendered":"http:\/\/3.209.169.194\/blogs\/joe\/?p=1180"},"modified":"2014-04-08T07:14:12","modified_gmt":"2014-04-08T14:14:12","slug":"finding-timeout-prone-code-max_elapsed_time","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/joe\/finding-timeout-prone-code-max_elapsed_time\/","title":{"rendered":"Finding Timeout-Prone Code with max_elapsed_time"},"content":{"rendered":"
Consider a scenario where your application timeout setting is 30 seconds and you\u2019ve been asked to proactively start tuning workloads that are at risk of timing out.\u00a0 There are several different places you can start, and I want to demonstrate an additional option today.<\/p>\n
To demonstrate timeout settings, I can configure it in SQL Server Management Studio via the \u201cExecution time-out\u201d setting:<\/p>\n