Skip to main content

70-562 Data Caching


If the data is control by other services, it can be delicate to cache.

Data can be cached and automaticaly updated when sql changes.

It depends on sql 2005 and later Query Notification, previous versions relies on database triggers.

ASP.Net can poll changes to the table, and sql can be configureged with Aspnet_regsql tool.

The the target table has to be configured with the aspnet_regsql tool, a changed id is added to the table.

Polls based caching is very reliable and easy to configure.


Datasource controls have properties to enable caching, this also requires the table to be configured with the aspreg tool.

Table caching caches only tables, not the page.

Can also be based on rows, to change only when specific row changes, for example products of a certain category. It will update only when this row is changed, this is custom caching rules.


QueryNotification caching doesnt require to configure sql. The service broker has to be enabled. Alter database northwind set service broker. Query notification also works in sql express.
A channel has to be created in teh glorbal.asax in the start you start SqlDependency.Start, and the opposite in stop.

QueryNotification can't use aggregates, image columns, cant use non detemrinistic functions like get date, cant use distinct, full name like dbo.tableName, no * in select have to be explicit with culumn names.

To use the datasource, use sqlcommandnotification as an attribute of the datasource, and this can be confugred from code, using SqlCAcheDependency.

Comments

Post a Comment

Popular posts from this blog

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.
Post a Comment
Read more

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.
4 comments
Read more

Object.create vs. Object.Assign

The two functions return a new Object but with a difference. Object.assign will go through an enumerable and copy it's properties. Object.create will create a new empty object but link it's proto chain to the old object. One way to view this is with JSON.stringify(newCreatedObject) this would return an empty object, since all the properties are not part of the object's own properties, but inherited through prototype inheritance. In both case, the advantage is it allows to extended existing objects without modifying the original. This is particularly important when receiving arguments from a caller, in this case it's better to use these methods instead of modifying the caller's object since he might have planned to use it again later, expecting it to be in it's original state.
Post a Comment
Read more