<?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>2008 on SQLNikon</title><link>https://sqlnikon.com/tag/2008/</link><description>Recent content in 2008 on SQLNikon</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Jan 2012 18:35:57 +0000</lastBuildDate><atom:link href="https://sqlnikon.com/tag/2008/index.xml" rel="self" type="application/rss+xml"/><item><title>Database Mail Configuration Error 264</title><link>https://sqlnikon.com/2012/01/22/database-mail-configuration-error-264/</link><pubDate>Sun, 22 Jan 2012 18:35:57 +0000</pubDate><guid>https://sqlnikon.com/2012/01/22/database-mail-configuration-error-264/</guid><description>&lt;p&gt;As most of you know, the Database Mail feature in SQL Server 2008 is the life blood of any notification system for your instances.  If Database Mail fails to send notifications, you may not be warned if a job fails, or worst, a backup job.  We had a server last week that was exhibiting a weird behavior within Database Mail.  I was receiving mail from all parts of the Database Mail environment except for Agent Job Notifications.  I was able to send test emails from Database Mail, able to receive maintenance plan summary reports and even receive emails from within maintenance plans using the notification task.  Why was Agent Job Notifications the only area that was mis-behaving?  As I started diagnosing the issue I checked the main areas that usually stumped me in the past:&lt;/p&gt;</description></item><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>