.NET S EFFECTS ON SQL SERVER AppDomain are part

.NET S EFFECTS ON SQL SERVER AppDomain are part of the same process. Unlike the technique used to isolate stored procedures, the AppDomain protects SQL Server from all misuse or malicious use of system resources. .NET code shares the advantage of compilation with extended stored procedures. .NET code is Just-In-Time compiled into machine instructions at execution time. .NET classes are objects to enable usage of object-oriented programming techniques. The execution engine controls storage allocation and memory management. This ensures that, short of a bug in the engine itself, .NET procedural code will never step on random memory buffers. In case of severe programmer error, the execution engine can always dispose of the offending thread or even an AppDomain without interfering while SQL Server continues to run without interruption. This is shown in Figure 1-2. Writing SQL Server procedural code is examined in detail in Chapters 3 and 4. SQL Server 2005 ships with an in-memory .NET data provider to optimize data access from managed procedural code. When using this provider, programmers have a choice of using .NET types or SQL types. Some .NET types, like System.Int32, require no conversion or marshaling, but some, such as System.Decimal, are not exact matches. The .NET classes in System.Data.SqlTypes correspond exactly to the corresponding SQL Server types. Using these types in .NET procedures means no type SQL Server Data Buffers Managed Code Stored Procedure Figure 1-2: Preventing Managed Code from Interfering with SQL Server Processing or Writing over Buffers

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

Bookmark the permalink.

Comments are closed.