Notification Services in SQL Server 2008 - Not so much... (Notification Services are gone from SQL Server 2008. Dead, gone, no more, say goodbye, etc, etc)

The Bit Bucket (Greg Low) - Notification Services isn't deprecated in SQL 2k8, it's gone

"...

It's a great set of posts but it's important to get the message out that in the next version of the product, Notification Services isn't just deprecated, it's gone. It isn't wise to use it for any new development work unless you're intending to stay on SQL Server 2005 for the life of your application.

..."

Tibor Karaszi - No Notification Services in SQL Server 2008

"...

Here's a quote from July CTP readme:

"SQL Server Notification Services will not be included as a component of SQL Server 2008, but will continue to be supported as part of the SQL Server 2005 product support life-cycle. Moving forward, support for key notification scenarios will be incorporated into SQL Server Reporting Services. Existing Reporting Services functionality, such as data driven subscriptions, addresses some of the notification requirements. Features to support additional notification scenarios may be expected in future releases. "

..."

 

Since I've been only focused on the new stuff SQL Server 2008 and haven't been playing with the CTP's I had missed this. I had always wanted to play with this. I guess it's a good thing I never invested much time in it...

It kinds of bugs me that a Service like this came and went so quickly (two rev's, SQL 2000 & 2005 and now no more). I totally understand that some features need to be fired and go away, but it still kinds of tastes bad, you know?

Still I guess I'd rather it go away than just go on life support, not "really" be supported and be a dead branch. And I guess I'd rather it be killed and those resources put into other more active and important areas (easy for me to say since I didn't invest much time in it). But is it dead because it sucked? Because it wasn't "stick a fork in it its done?" Or because there wasn't enough interest internally and externally to push it?

That's the problem with hard decisions like this... They are... hard...  Still I'd rather a decision than some passive-aggressive limbo. Right one, wrong one, but at least make one... And they made one.

 

But how am I going to feel about using the "Next Cool Thing" in SQL Server?