.NET S EFFECTS ON SQL SERVER different languages can

.NET S EFFECTS ON SQL SERVER different languages can completely interoperate if written to the Common Language Specification (CLS). Even though language features might be radically different as in Managed C++, where managed and unmanaged code can be mixed in the same program the feature sets are similar enough that an organization can choose the language that makes the most sense without losing features. In addition, .NET code can interoperate with existing COM code (via COM-callable wrappers and runtime-callable wrappers) and arbitrary Windows Dynamic Link Libraries (DLLs) through a mechanism known as Platform Invoke (PInvoke). So .NET with managed code is so compelling because it improves developer productivity and the reliability and security of applications, provides interoperability between a wide variety of languages, and supports use of legacy Windows code not written using .NET. .NET s Effects on SQL Server What does this mean with respect to SQL Server, Microsoft s flagship database management system (DBMS)? Originally, SQL Server shared a common ancestry with the Sybase database. SQL Server version 7 was split off from this common ancestry and rewritten using component-based programming. This makes adding new features at any level of functionality easier. Prior to version 7, SQL Server was a monolithic application. SQL Server version 7 factored code into layers, with communication between the relational and storage engines accessible through OLE DB. The SQL Server 7 component-based architecture is shown in Figure 1-1. In addition to easing accommodation of new features in future versions, such as SQL Server 2005, the new component-based model offered a variety of form factors, from the SQL Server Enterprise Edition, which provides a data store for an entire enterprise, to Microsoft Data Engine (MSDE), which provides a data store for a single application. Separation of the relational engine from the storage engine in SQL Server 7 made it easier to accommodate other data sources, such as Exchange or WebDav, which are traditionally not thought of as databases. SQL Server s relational engine can load OLE DB Rowsets from an Exchange or WebDav store just as though it were processing data managed by the storage engine. In versions of SQL Server prior to SQL Server 2005, there were two ways to write programs that ran in SQL Server: Transact-SQL (T-SQL) and extended stored procedures. T-SQL is Microsoft s proprietary implementation of Persistent Stored Modules (SQL-PSM) as defined in SQL standards.

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Cheap Web Hosting services

Bookmark the permalink.

Comments are closed.