<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Sp_BliztFirst on SQLNikon</title><link>https://sqlnikon.com/tag/sp_bliztfirst/</link><description>Recent content in Sp_BliztFirst on SQLNikon</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 10 Jan 2018 11:25:55 +0000</lastBuildDate><atom:link href="https://sqlnikon.com/tag/sp_bliztfirst/index.xml" rel="self" type="application/rss+xml"/><item><title>Spectre/Meltdown Baselining</title><link>https://sqlnikon.com/2018/01/10/spectre-meltdown-baselining/</link><pubDate>Wed, 10 Jan 2018 11:25:55 +0000</pubDate><guid>https://sqlnikon.com/2018/01/10/spectre-meltdown-baselining/</guid><description>&lt;p&gt;&lt;a href="https://blobeater.blog/2018/01/02/t-sql-tuesday-98-your-technical-challenges-conquered/"&gt;&lt;img src="https://sqlnikon.com/wp-content/uploads/2014/01/t-sql-tuesday.png" class="alignleft wp-image-630 size-full" width="150" height="150" /&gt;&lt;/a&gt;This month’s #tsql2sday is being hosted by Arun Sirpal (&lt;a href="https://blobeater.blog"&gt;b&lt;/a&gt;|&lt;a href="https://twitter.com/blobeater1"&gt;t&lt;/a&gt;). The topic this month is how we conquered a technical challenge. The area I’ve been spending the most time in recently is baselining for the Spectre/Meltdown patches that are coming. We have a monitoring tool from &lt;a href="https://www.idera.com/productssolutions/sqlserver/sqldiagnosticmanager"&gt;Idera&lt;/a&gt;, SQL Diagnostic Manager, on our key production boxes but I wanted something consistent across all boxes that we could use for tracking and baselining wait types.&lt;/p&gt;</description></item></channel></rss>