History of Microsoft SQL Server: Difference between revisions

Content deleted Content added
Holy shizzle! Yet another ESU announcement. Obviously, the employees have no idea what "the hack" they're doing.
Was was spelled "ws"
Line 224:
 
===SQL Server 2005===
SQL Server 2005 (formerly codenamed "Yukon") wswas released in November 2005. It included native support for managing [[XML]] data, in addition to [[relational database|relational data]]. For this purpose, it defined an <code>xml</code> [[data type]] that could be used either as a data type in database columns or as [[Literal (computer science)|literal]]s in queries. XML columns can be associated with [[XSD]] schemas; XML data being stored is verified against the schema. XML data is queried using [[XQuery]]; SQL Server 2005 added some extensions to the [[T-SQL]] language to allow embedding XQuery queries in T-SQL. It also defines a new extension to XQuery, called XML DML, that allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over [[web service]]s using [[Tabular Data Stream]] (TDS) packets encapsulated within [[SOAP (protocol)]] requests. When the data is accessed over web services, results are returned as XML.<ref name="Database Engine XML Enhancements">{{cite web|url=http://msdn.microsoft.com/en-us/library/ms170809.aspx|title=Database Engine XML Enhancements|accessdate=December 3, 2007}}</ref>
 
[[Common Language Runtime]] (CLR) integration was introduced with this version, enabling one to write SQL code as Managed Code by the CLR. For relational data, [[T-SQL]] has been augmented with error handling features (try/catch) and support for recursive queries with CTEs (Common Table Expressions). SQL Server 2005 has also been enhanced with new indexing algorithms, syntax and better error recovery systems. Data pages are [[checksum]]med for better error resiliency, and optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a [[Cluster (computing)|cluster]] is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET Framework.<ref name="Database Engine Enhancements">{{cite web|url=http://msdn.microsoft.com/en-us/library/ms170910.aspx|title=Database Engine Enhancements|accessdate=December 3, 2007}}</ref>