Global

Cache items with this priority level are likely to be deleted from the cache as the server frees system memory only after those items with Low or BelowNormal priority. This is the default.

Cache items with this priority level are the most likely to be deleted from the cache as the server frees system memory.

Cache items with this priority level are more likely to be deleted from the cache as the server frees system memory than items assigned a Normal priority.

Cache items with this priority level are less likely to be deleted as the server frees system memory than those assigned a Normal priority.

Cache items with this priority level are the least likely to be deleted from the cache as the server frees system memory.

The cache items with this priority level will not be deleted from the cache as the server frees system memory.

The default value for a cached item's priority is Normal.

The item is removed from the cache because a file or key dependency changed.

The item is removed from the cache because it expired.

The item is removed from the cache by a Cache.Remove method call or by an Cache.Insert method call that specified the same key.

The item is removed from the cache because the system removed it to free memory.

The item is removed from the cache because the its dependency was invalid.

receive notifications when member joined

receive notifications when member left

receive notifications when cacheis stoped

receive all notifications

In "Pessimistic" mode of synchronization, client cache always checks for the "version" of the cached item before returning it to the application.

It is possible that client caches are not synchronized with clustered cache for a small period of time. If during this time users gets an item from the client cache, he may get an old version. This is the "Optimistic" mode of synchronization

System.Int64. A 64-bit signed integer.

System.Array of type System.Byte. A fixed-length stream of binary data ranging between 1 and 8,000 bytes.

An unsigned numeric value that can be 0, 1, or null.

A fixed-length stream of non-Unicode characters ranging between 1 and 8,000 characters.

Date and time data ranging in value from January 1, 1753 to December 31, 9999 to an accuracy of 3.33 milliseconds.

A fixed precision and scale numeric value between -10 38 -1 and 10 38 -1.

A floating point number within the range of -1.79E +308 through 1.79E +308.

A 32-bit signed integer.

A currency value ranging from -2 63 :or -9,223,372,036,854,775,808 to 2 63 -1 :or +9,223,372,036,854,775,807 with an accuracy to a ten-thousandth of a currency unit.

A fixed-length stream of Unicode characters ranging between 1 and 4,000 characters.

A variable-length stream of Unicode characters ranging between 1 and 4,000 characters. Implicit conversion fails if the string is greater than 4,000 characters. Explicitly set the object when working with strings longer than 4,000 characters.

A floating point number within the range of -3.40E +38 through 3.40E +38.

A globally unique identifier :or GUID.

Date and time data ranging in value from January 1, 1900 to June 6, 2079 to an accuracy of one minute.

A 16-bit signed integer.

A currency value ranging from -214,748.3648 to +214,748.3647 with an accuracy to a ten-thousandth of a currency unit.

Automatically generated binary numbers, which are guaranteed to be unique within a database. timestamp is used typically as a mechanism for version-stamping table rows. The storage size is 8 bytes.

An 8-bit unsigned integer.

A variable-length stream of binary data ranging between 1 and 8,000 bytes. Implicit conversion fails if the byte array is greater than 8,000 bytes. Explicitly set the object when working with byte arrays larger than 8,000 bytes.

A variable-length stream of non-Unicode characters ranging between 1 and 8,000 characters.

A special data type that can contain numeric, string, binary, or date data as well as the SQL Server values Empty and Null, which is assumed if no other type is declared.

An XML value.

A SQL Server 2005 user-defined type :UDT.

A special data type for specifying structured data contained in table-valued parameters.

Date data ranging in value from January 1,1 AD through December 31, 9999 AD.

Time data based on a 24-hour clock. Time value range is 00:00:00 through 23:59:59.9999999 with an accuracy of 100 nanoseconds.

Date and time data. Date value range is from January 1,1 AD through December 31, 9999 AD. Time value range is 00:00:00 through 23:59:59.9999999 with an accuracy of 100 nanoseconds.

Date and time data with time zone awareness. Date value range is from January 1,1 AD through December 31, 9999 AD. Time value range is 00:00:00 through 23:59:59.9999999 with an accuracy of 100 nanoseconds. Time zone value range is -14:00 through +14:00.

An SQL text command. (Default.)

The name of a stored procedure.

The name of a table.

This specifies that no data or meta data is required when an event notification is raised.

This specifies that item of collection is required when an event notification is raised.

data will be delivered asynchronously

data will be delivered synchronously

Delivers message to all registered subscribers, if no subscriber has been registered, it will return without any failure acknowledgment. Message will be sent to any subscriber when it registers on topic; unless message expiration has not occurred.

Delivers message to any one of the registered subscribers. If acknowledgement is not received, the message is reassigned to another subscriber till it reaches its expiration time limit.

For distributed list.

For distributed queue.

For distributed counter.

Specifies that the entry under question is a cache item.

Specifies that the entry under question is a collection item of type list.

Specifies that the entry under question is a collection item of type queue.

Specifies that the entry under question is a collection item of type set.

Specifies that the entry under question is a collection item of type dictionary.

Specifies that the entry under question is a collection item of type counter.

Specifies that the entry under question has no type.

This specifies that no data or meta data is required when an event notification is raised.

This specifies that only meta data of cache item is required when an event notification is raised. Meta data includes in information like groups, subgroups, cacheItemPriority, item version etc.

This specifies that the value of the cache item is required along with all the meta data when an event notification is raised.

User receives a notification when an item is added in cache.

when an item is updated in cache.

User receives a notification when an item is removed from cache.

Indicates that no expiration is to take place.

Indicates that item expiration in cache is to follow idle expiration.

Indicates that item expiration in cache is to follow fixed expiration.

Indicates that item expiration in cache is to follow fixed expiration and value should be taken from 'DefaultAbsolute' field in NCache Manager.

Indicates that item expiration in cache is to follow fixed expiration and value should be taken from 'DefaultAbsoluteLonger' field in NCache Manager.

Indicates that item expiration in cache is to follow fixed expiration and value should be taken from 'DefaultSliding' field in NCache Manager.

Indicates that item expiration in cache is to follow fixed expiration and value should be taken from 'DefaultSlidingLonger' field in NCache Manager.

Isolation level of Cache will be read from the configuration file.

InProc specifies low Isolation level i.e Cache process is embeded inside the application process.

OutProc specifies high isolation level i.e Cache process runs in a seprate process.

Trigger key dependency when an update or remove operation takes place on the cache item. This is the default value.

Trigger key dependency when a remove operation takes place on the cache item.

log level will be set to information

log level will be set to error

log level will be set to debug

Failed because it got evicted before delivery.

Failed because it could not be delivered within expiration time.

The BFILE datatype stores unstructured binary data in operating-system files outside the database. A BFILE column or attribute stores a file locator that points to an external file containing the data. The amount of BFILE data that can be stored is limited by the operating system.

The BLOB datatype stores unstructured binary data in the database. BLOBs can store up to 128 terabytes of binary data.

Allows whole numbers from 0 to 255

The CHAR datatype stores fixed-length character strings. String length (in bytes or characters) is between 1 and 2000 bytes. The default is 1 byte.

The CLOB datatypes store up to 128 terabytes of character data in the database. CLOBs store database character set data.

The Date datatype stores point-in-time values (dates and times) in a table. The Date datatype stores the year (including the century), the month, the day, the hours, the minutes, and the seconds (after midnight).

Decimal number datatype.

64-bit, double-precision floating-point number datatype.

A 16-bit signed integer.

A 32-bit signed integer.

A 64-bit signed integer.

Interval Day to Second literal.

Interval Year to Month Literal.

Long can store variable-length character data containing up to 2 gigabytes of information. Long data is text data that is to be appropriately converted when moving among different systems.

The LONG RAW datatypes is used for data that is not to be interpreted (not converted when moving data between different systems) by Oracle Database. These datatypes are intended for binary data or byte strings.

The maximum length of an NCHAR column is 2000 bytes. It can hold up to 2000 characters. The actual data is subject to the maximum byte limit of 2000. The two size constraints must be satisfied simultaneously at run time.

The NCLOB datatypes store up to 128 terabytes of character data in the database. NCLOBs store Unicode national character set data.

The maximum length of an NVARCHAR2 column is 4000 bytes. It can hold up to 4000 characters. The actual data is subject to the maximum byte limit of 4000. The two size constraints must be satisfied simultaneously at run time.

The Raw datatype is used for data that is not to be interpreted (not converted when moving data between different systems) by Oracle Database. These datatypes are intended for binary data or byte strings.

A REF CURSOR is a PL/SQL data type whose value is the memory address of a query work area on the database.

Single byte character sets.

Timestamp WITH LOCAL TIME ZONE is stored in the database time zone. When a user selects the data, the value is adjusted to the user's session time zone.

Get the system date and time accroding to the timezone returned in a Timestamp datatype.

The VARCHAR2 datatype stores variable-length character strings. Maximum string length (in bytes or characters) is between 1 and 4000 bytes for the VARCHAR2 column.

XMLType can be used like any other user-defined type.

Text SQL statement to execute against the database.

When the CommandType property is set to StoredProcedure, the CommandText property should be set to the name of the stored procedure.

In parameters.

Out parameters.

Return null if item not found.

Look data source for item if not found.

Forcefully look data source for item and update/add item in cache.

Specifies the default option settings for SqlString comparisons.

Specifies that SqlString comparisons must ignore case.

Specifies that SqlString comparisons must ignore nonspace combining characters, such as diacritics. The Unicode Standard defines combining characters as characters that are combined with base characters to produce a new character. Non-space combining characters do not use character space by themselves when rendered. For more information about non-space combining characters, see the Unicode Standard at http://www.unicode.org.

Specifies that SqlString comparisons must ignore the Kana type. Kana type refers to Japanese hiragana and katakana characters that represent phonetic sounds in the Japanese language. Hiragana is used for native Japanese expressions and words, while katakana is used for words borrowed from other languages, such as "computer" or "Internet". A phonetic sound can be expressed in both hiragana and katakana. If this value is selected, the hiragana character for one sound is considered equal to the katakana character for the same sound.

Specifies that SqlString comparisons must ignore the character width. For example, Japanese katakana characters can be written as full-width or half-width and, if this value is selected, the katakana characters written as full-width are considered equal to the same characters written in half-width.

Performs a binary sort

Specifies that sorts should be based on a characters numeric value instead of its alphabetical value

An SQL text command. (Default.)

The name of a stored procedure.

The row contains its original values.

The row contains current values.

The row contains a proposed value.

The default version of System.Data.DataRowState. For a DataRowState value of Added, Modified or Deleted, the default version is Current. For a System.Data.DataRowState value of Detached, the version is Proposed.

Used for Input variables. The value will be passed from calling environment. This is the default.

Used for Output variable and value will be returned to calling environment.

The parameter can perform both input and output.

The parameter represents a return value from an operation such as a stored procedure, built-in function, or user-defined function.

Shared subscription policy is for multiple subscribers on a single subscription. In this case messages are sent to any of the topic subscribers. This policy provides better load division over clients subscribing to a subscription.

Exclusive subscription policy is for a single subscriber on a single subscription. In this case messages are recieved by the single subscriber only.

Search objects that have all of the tags in common.

Search objects that have any of the specified tags in common.

set priority for topic as Low

set priority for topic as Normal

set priority for topic as High

Search by name.

Search by pattern.

If user code returned false

If write behind operation was successful

Does not update data source.

Updates data source synchronously.

Updates data source asynchronously.

To log the Add Items operations in write behind.

To log the Update Items Operations in write behind.

To log the Delete operations in write behind.