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

Popular posts from this blog

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.

70-562 ListView

List View is a versatile control that allows to work with a signle control rather than many smaller controls. Provides rich sorting, deleting, editing, it is one of the most flexible grid control. Design view can fill the ListView with fake data to give an overview. In designer, the configure list view link might not show, (currently a bug), to fix configure the datasource but cancel then click configure datasource again and this time click finish and the Cofnoigure ListView link will show up in the smarttag. You can choose templates, LayoutTemplate is crucial, ItemTemplate(a row is part of a table, in a list view they are called items since they don't have to correspond to a table row), AlternatingItemTemplate, ItemSeparatorTemplate, SelectedItem, EmptyItemTemplate, EditItemTemplate, InsertItemTemplate allows to customize what the user will be presented when creating an item, EmptyDataTemplate. The itemPlaceHolder and the groupPlaceHolder are important elements as the will b...

70-562 Tracing

Tracing can be enabled from the page directive, programmatically or from the web.config. This will append the trace info to the bottom of the page. There several tables of grouped trace information: Life cycle events, controls used by page, sessions state, cookies, http reuqest headers, server variables. SessionID, Time spent in each event, and check that the events are executing in the expected order. The control tree give a hierarchy of the controls in the page, and how much the control is using in the viewstate, and render by tells how much room the control uses on the page. See cookie information. And can see the Header information incase you do any kind of header manipulation. Also see query string collection. Also see the server variables passed back and forth between the server and the client application, logon user, remote user. Enable tracing when not in production, (remember to disable it when building a release... that and the debug= true setting get forg...