Glossary

Glossary
.NET Framework
Microsoft defines Microsoft .NET as a set of Microsoft software technologies for connecting information, people, systems, and devices. To optimize software integration, the .NET Framework uses small, discrete, building-block applications called Web services that connect to each other as well as to other, larger applications over the Internet.
The .NET Framework has two key parts:
ADO.NET
The data access component for the .NET Framework. ADO.NET is made of a set of classes that are used for connecting to a database; providing access to relational data, XML, and application data; and retrieving results.
ADO.NET Entity Framework
An object-relational mapping (ORM) framework for the .NET Framework. Developers can use it to create data access applications by programming against a conceptual application model instead of programming directly against a relational storage schema. This model allows developers to decrease the amount of code that must be written and maintained in data-centric applications.
assembly
A compiled representation of one or more classes. Each assembly is self-contained, that is, the assembly includes the metadata about the assembly as a whole. Assemblies can be private or shared.
assembly cache
A machine-wide code cache that is used for storing assemblies side-by-side. The cache is in two parts. The global assembly cache contains assemblies that are explicitly installed to be shared among many applications on the computer. The download cache stores code that is downloaded from Internet or intranet sites, which is isolated to the application that downloaded the code.
authentication
The process of identifying a user, typically based on a user ID and password. Authentication ensures that users are who they claim to be. See also client authentication, NTLM authentication, OS authentication, and user ID/password authentication.
bulk load
A method of inserting large amounts of data into a database table. Rows are sent from the database client to the database server in a continuous stream. The database server can optimize how rows are inserted. Also known as bulk copy.
client authentication
The process of identifying the user ID and password of the user logged onto the system on which the driver is running to authenticate the user to the database. The database server depends on the client to authenticate the user and does not provide additional authentication. See also authentication.
ClickOnce Deployment
A feature of the .NET Framework 2.0 that lets clients download the assemblies they need from a remote web server. The first time the assembly is referenced, it is downloaded to a cache on the client and executed. After that, when a client accesses the application, the application checks the server to find out whether any assemblies have been updated. Any new assemblies are downloaded to the download cache on the client, refreshing the application without any interaction with the end user.
client load balancing
A mechanism that distributes new connections in a computing environment so that no given server is overwhelmed with connection requests.
code access security (CAS)
A mechanism that is provided by the common language runtime through which managed code is granted permissions by a security policy; permissions are enforced, limiting the operations that the code will be allowed to perform.
Code First model
A development concept that is focused around defining your model using C#/Visual Basic .NET classes. These classes can then be mapped to an existing database or be used to generate a database schema. Additional configuration can be supplied using Data Annotations or via a fluent API.
collection
A set of similarly typed objects that are grouped together. For example, data collections include hash tables, queues, stacks, dictionaries, and lists. Some collections have specialized functions, such as the MetaDataCollection collections.
common language runtime (CLR)
The common language runtime (CLR) is the core runtime engine in the Microsoft .NET Framework. The CLR supplies services such as cross-language integration, code access security, object lifetime management, and debugging support. Applications that run in the CLR are sometimes said to be running "in the sandbox."
connection failover
A mechanism that allows an application to connect to an alternate, or backup, database server if the primary database server is unavailable, for example, because of a hardware failure or traffic overload.
connection retry
Connection retry defines the number of times the data provider attempts to connect to the primary and, if configured, alternate database servers after the initial unsuccessful connection attempt. Connection retry can be an important strategy for system recovery.
connection pooling
The process by which connections can be reused rather than creating a new one every time the data provider needs to establish a connection to the underlying database.
Data Access Application Block (DAAB)
A pre-defined code block that provides access to the most often used ADO.NET data access features. Applications can use the application block to pass data through application layers, and submit changed data back to the database.
data provider
An ADO.NET data provider communicates with the application and database and performs tasks such as establishing a connection to a database, executing commands, and returning results to the application.
destination table
In a DataDirect Bulk Load operation, the table on the database server into which the data is copied.
entity
A pre-defined code block that provides access to the most often used ADO.NET data access features. Applications can use the application block to pass data through application layers, and submit changed data back to the database.
Global Assembly Cache (GAC)
The part of the assembly cache that stores assemblies that are specifically installed to be shared by many applications on the computer. Applications deployed in the Global Assembly Cache (GAC) must have a strong name to handle name and version conflicts.
isolation level
A particular locking strategy that is employed in the database system to improve data consistency. The higher the isolation level number, the more complex the locking strategy behind it. The isolation level provided by the database determines how a transaction handles data consistency.
The American National Standards Institute (ANSI) defines four isolation levels:
Kerberos authentication
An OS authentication protocol that provides authentication using secret key cryptography. See also authentication and OS authentication.
load balancing
See client load balancing.
locking level
A database operation that restricts a user from accessing a table or record. Locking is used in situations when more than one user might try to use the same table at the same time. By locking the table or record, the system ensures that only one user at a time can affect the data.
Logging Application Block (LAB)
A component of the Microsoft Enterprise Libraries that simplifies the implementation of common logging functions. Developers can use the Logging Block to write information to a variety of locations, such as the event log, an e-mail message, or a database.
managed code
Code that is executed and managed by the .NET Framework, specifically by the CLR. Managed code must supply the information necessary for the CLR to provide services such as memory management and code access security.
metadata
Information about data, for example, a database schema that describes the fields, columns, and formats used in a database. Different database schema elements are exposed through schema collections.
Model First model
A development concept that is focused on the ability to start with a conceptual model and create the database from it. Additional configuration can be supplied using Data Annotations or through a fluent API.
namespace
A logical naming scheme for grouping related types. The .NET Framework uses a hierarchical naming scheme for grouping types into logical categories of related functionality, such as the ASP.NET technology or remoting functionality. Design tools can use namespaces to make it easier for developers to browse and reference types in their code. A single assembly can contain types whose hierarchical names have different namespace roots, and a logical namespace root can span multiple assemblies. In the .NET Framework, a namespace is a logical design-time naming convenience, whereas an assembly establishes the name scope for types at run time.
No-Touch Deployment
A feature of the .NET Framework 1.x that lets clients download the assemblies they need from a remote web server. The first time the assembly is referenced, it is downloaded to a cache on the client and executed. After that, when a client accesses the application, the application checks the server to find out whether any assemblies have been updated. Any new assemblies are downloaded to the download cache on the client, refreshing the application without any interaction with the end user.
NTLM authentication
A network authentication protocol that provides a challenge response security mechanism for connections between Windows clients and servers, confirming the user’s identification to a network service. It is used in later versions of Windows for backward compatibility. See authentication and OS authentication.
OS authentication
An authentication process that can take advantage of the user name and password that is maintained by the operating system to authenticate users to the database or use another set of user credentials specified by the application. By allowing the database to share the user name and password that is used for the operating system, users with a valid operating system account can log into the database without supplying a user name and password. See also authentication, Kerberos authentication, and NTLM authentication.
Performance Monitor
A tool in the Windows SDK that identifies areas in which performance problems exist.
Performance Tuning Wizard
A component that is built into DataDirect Connect for ADO.NET and accessible through Visual Studio that leads you through a series of questions about your application. Based on your answers, the Wizard provides the optimal settings for DataDirect Connect for ADO.NET connection string options that affect performance. Optionally, you can generate a new application that is pre-configured with a connection string that is optimized for your environment.
schema collection
Closely related schemas that can be handled more efficiently when grouped together. Database schema elements such as tables and columns are exposed through schema collections.
Secure Socket Layer (SSL)
An industry-standard protocol for sending encrypted data over database connections. SSL secures the integrity of your data by encrypting information and providing SSL client/SSL server authentication.
stream
An abstraction of a sequence of binary or text data. The Stream class and its derived classes provide a generic view of these different types of input and output.
strong name
A name that consists of an assembly's text name, version number, and culture information (if provided), with a public key and a digital signature generated over the assembly. Assemblies with the same strong name must be identical.
unmanaged code
Code that is executed directly by the operating system, outside of the CLR. Unmanaged code includes all code written before the .NET Framework was introduced. Because it is outside the .NET environment, unmanaged code cannot make use of any .NET managed facilities such as memory management and code access security.
user ID/password authentication
Authentication process that authenticates the user to the database using a database user name and password. See also authentication.