SQL Server Notification Services
Late yesterday afternoon, Microsoft posted to their download site a Release Candidate (RC1) for the Notification Services Components Package. This is essentially the same package that was released back in February 2007, with one really major exception - it supports SQL Server 2008!
As one who has worked quite a bit with Notification Services (and still I received calls and emails from around the world regarding Notification Services), I'm very glad to see this. Not only because I'm glad to see a good feature persisted a bit longer, but because Microsoft stepped up and in my opinion made good on an...
As most you already know, Notification Services is not part of Microsoft SQL Server 2008. I think this is a shame since SSNS is really a great product. It may be rather complex at first glance, but it's a great product nonetheless. I'll probably devote a blog to it's abrupt deprecation at some point in the future.
In the meantime, if you're preparing to upgrade to SQL Server 2008, you should verify that you don't have any rogue SSNS instances running on any of your servers. I hope your environment is more controlled than that, but I've seen more...
Last week, I completed an upgrade of a SQL Server 2000 server to SQL Server 2005. Not really a big deal; servers are routinely upgraded to a newer version of software. Sometimes it seems the upgrades come too quickly. Other times it seems like we are waiting for the proverbial pot of water to boil while eagerly looking forward the next release.
This server, however, included a Notification Services instance. It got me to thinking about upgrades and some of the changes in SSNS between v2.0 and 2005. I've compiled a "Top 10" list of enhancements to SSNS 2005. (I...
The old adage "An ounce of prevention is worth a pound of cure" can be applied to many topics and areas of life. And while it has its origins in personal health care, nowhere is it more true than in an IT shop. Whether you're talking about high availability solutions or starting with a good database design, planning ahead is well worth the effort. Anyone who has been through an IT crisis can testify to that!
But alas, we live in a dynamic world and we can only make calculated guesses at what the the ounce of prevention should be....
One the more welcomed enhancements of SQL Server 2005 Notification Services was the new Microsoft.SqlServer.Management.Nmo namespace. The namespace provides classes that may be used develop and administer SSNS instances and applications.
For example, the following C# console application may be used to iterate through each SSNS instance of a SQL Server 2005 instance, printing its name to the console window. If you'd like to try this code for yourself, don't forget to add a reference to the microsoft.sqlserver.smo.dll in your Visual Studio 2005 project.
In my initial post here on the SQLTeam site, I mentioned that for the prior three years I had blogged on another site. That blog was almost exclusively dedicated to SQL Server Notification Services.
If you are a regular reader of this new blog, you've undoubtedly noticed that I've broadened the scope to include topics of interest to DBAs, database developers, and general technologists.
As time permits, I'm still attempting to recover the SSNS tutorials and commentary from my prior blog. I'll post what I can recover as it becomes available.
In the meantime, here are a few links to...
Even though SQL Server 2008 does not include the Notification Services (SSNS) component, it seems that companies still consider SSNS a very viable option for upcoming notification projects. I'm planning to write a blog or SQLTeam article in the near future to address some questions I'm frequently asked.
In the meantime, if you have decided to create a new notification application using SSNS, I'm reposting a short tutorial I created a couple of years ago. It's been modified and updated slightly.
In this blog we'll go through the simple steps that can be used to create a new SQL...
Microsoft's Ken Henderson hosted a web cast called “Introducing Notification Services in SQL Server 2005”. It was recorded three years, but it’s still a great material. If you’ve ever sat in on one of his sessions at PASS, you know he’s a great presenter.
Of course much to my and other's chagrin, SQL Server Notification Services is not part of the SQL Server 2008 product. Perhaps that will become the fodder for another post.
In the meantime, enjoy the web cast!
Thanks to all of you who attended the DevLink Technical Conference in Nashville, Tennessee! It was great to see such a turnout for the event. Big kudos goes to all those who carried the load and championed this event. Putting on an event like this is no minor task and is definitely a labor of love.
As promised in my session, here are the presentation materials I used - the slide deck and the demo scripts.
I hope you found it worth your while.
Have you ever been troubleshooting a SQLNS instance and noticed the status code column in some of the views and underlying tables? For example, the NSSMTPNotifications view has a column named DeliveryStatusCode with a values that range from 0 to 6. But what does that mean? What does a value of 6 actually tell you?
Fortunately, the SSNS database contains tables with status code descriptions. Try running the following query in your application database. Note: you'll need to replace dbo with the appropriate schema name.
SELECT * FROM dbo.NSNotificationDeliveryStatusCodes
Figure 1 shows the results. You can see that a value of 6 in...
Full Notification Services Archive