Doug Reilly's Weblog

Embedded Reporting of the Information Age...

Rob Howard - Database Geek of the Week!

This week, I have posted a very cool Database Geek of the Week Interview with Rob Howard.  From the interview:

Doug: Can you think of a cool tip or trick for the developers who will be working with the latest SQL Server 2005 Beta?

Rob: Easy: the ability of SQL Server 2005 to send notifications to applications when the results of a query, stored procedure or view change. For ASP.NET developers, this feature, coupled with caching, equals database cache invalidation. To be notified when data cached by ASP.NET is no longer valid will fundamentally change the way software is written.

Read the full interview here.

Posted: Jul 27 2005, 08:00 AM by douglas.reilly | with 5 comment(s)
Filed under: ,

Comments

Joe said:

> this feature, coupled with caching, equals database cache invalidation...
I understood (and hope I'm right) that Whidbey Database Cache Invalidation works with SQL Server 2000. If so, this is not a SQL Server 2005 feature...
# July 27, 2005 10:53 AM

Douglas Reilly said:

The feature is available when ASP.NET connects to SQL Server 2000, however, the implementation is different and a little less flexible. I am sure Rob will correct me if I am wrong...
# July 27, 2005 10:57 AM

Eric Newton said:

"To be notified when data cached by ASP.NET is no longer valid will fundamentally change the way software is written."

How do you figure? As if we havent been invalidating data to begin with? Sounds like Rob's about to generate some Telligent hype.

Yeah Community Server! Yeah for taking a simple concept and transmorgrifying it into a mess. (In some ways typical of overzealous developement)
# July 27, 2005 11:15 AM

Douglas Reilly said:

I think Rob's implication here is that it is lots easier to do. Previously, you had to rely upon timing or some sort of manual mechanism to invalidate a cache entry that is caching information from a database...
# July 27, 2005 11:54 AM

Erik Porter said:

Joe, yes it is available for SQL Server 2000, but as Doug mentioned, it's different. SQL Server 2005 actually sends out a notification letting ASP.NET know that the cache should be invalidated when the data changes. SQL Server 2000 does not have this feature so the ASP.NET process polls the SQL Server to know when there are data changes. This isn't quite as efficient as a notification (push), but it is still a huge performance gain over no cache at all.
# July 27, 2005 1:44 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)