M

   

mainframe computer

merging

Microsoft development environment

Microsoft Solutions Framework (MSF)

Microsoft Transaction Server (MTS)

mixed cursor

mixed security

mainframe computer

A very large computer with many users. Before PCs were available, the term "mainframe" meant the cabinet containing the central processor unit (CPU) of the large computer. Still commonly used in enterprise contexts, mainframes can be accessed from Windows NT through the COM Transaction Integrator (COMTI).

merging

In source control, a process of combining differences in two or more changed copies of a file into a new version of the file. A merge involves at least two different files (which can be different versions of the same file or changes made to the same version of the file) and creates a new file made up of the results of the merge.

Microsoft development environment

The integrated development environment through which you use Microsoft® Visual InterDev™, Visual J++™, and accompanying tools.

Microsoft Solutions Framework (MSF)

A development framework produced by Microsoft Consulting Services (MCS). MSF is based on Microsoft's internal development methodology as well as the practices of hundreds of MCS corporate clients.

Microsoft Transaction Server (MTS)

A component-based transaction processing system for developing, deploying, and managing server applications. MTS defines a programming model for developing distributed, component-based applications. It also provides a run-time infrastructure and a graphical tool for deploying and managing these applications.

mixed cursor

A keyset/dynamic cursor in which the keyset is smaller than the result set, but larger than the rowset. When a mixed cursor scrolls beyond the boundaries of the keyset, it becomes dynamic; that is, the driver simply retrieves the next rowset.

mixed security

A security mechanism in which SQL Server login requests can be validated using either integrated or standard security methods. Both trusted connections (as used by Windows NT integrated security) and nontrusted connections (as used by standard security) are supported. When a user attempts to log in to the server over a trusted (multi-protocol or named pipes) connection, SQL Server examines the login name to determine if integrated or standard security mechanisms should be used.