<?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>Brent Ozar on SQLNikon</title><link>https://sqlnikon.com/tag/brent-ozar/</link><description>Recent content in Brent Ozar on SQLNikon</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 31 Dec 2011 23:17:02 +0000</lastBuildDate><atom:link href="https://sqlnikon.com/tag/brent-ozar/index.xml" rel="self" type="application/rss+xml"/><item><title>2011 was the year of #SQLFamily</title><link>https://sqlnikon.com/2011/12/31/2011-was-the-year-of-sqlfamily/</link><pubDate>Sat, 31 Dec 2011 23:17:02 +0000</pubDate><guid>https://sqlnikon.com/2011/12/31/2011-was-the-year-of-sqlfamily/</guid><description>&lt;p&gt;As the name suggests, SQL Family feels like family.  There is no other professional organization in the world that supports a product line as well as #SQLFamily.  My introduction to #SQLFamily was in the summer of 2011 when I decided to get back into SQL Server full-time after going to the dark side, management, for the two previous years.  I had a strong background in SQL Server 2000 &amp;amp; 2005 but not the full-time experience under 2008 &amp;amp; 2008 R2.&lt;/p&gt;</description></item></channel></rss>