Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Proactive caching scheduled notification not working Expand / Collapse
Author
Message
Posted Saturday, May 25, 2013 12:22 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, May 23, 2014 7:58 AM
Points: 115, Visits: 210
Hi can anyone tell me how scheduled notification works.I tried to work on it but did not understand polling query and processing query concept behind it.
Post #1456764
Posted Sunday, June 9, 2013 5:46 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 11:45 PM
Points: 7,094, Visits: 12,582
The old school way uses polling. The .net framework will check a table to see if it has changed data since the last time it was polled. If it has changed, .net will clear the cached data so the next time its requested it will be retrieved from the database again, instead of using the cached data.

The new school way to do the same thing is to have the database engine notify the .net application by leveraging Event Notifications subsystem within SQL Server. This way as soon as a cached object is invalidated by database activity the application will be notified, I.e. No polling.


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1461363
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse