文档介绍：学校代码: XXX
学号:XXX
本科毕业设计外文文献翻译
(
学生姓名:XXX
学院:信息工程学院
系别:计算机系
专业:软件工程
班级:软件06班
指导教师:XXX 讲师
本文源码索取,请联系qq:68661508
二〇一〇年六月
Pro SQL Server2008 XML
SQL Server 2008’s native XML manipulation and querying facilities are particularly usefulin the following situations:
• You want to manipulate or share XML data while taking advantage of SQL Server’stransactional capabilities.
• You want to take advantage of SQL Server’s administrative functionality to back up,recover, or replicate your XML data.
• You need to ensure that your server-side XML data is valid and well-formed.
• You want your XML and relational data to interoperate.
• You want to take advantage of SQL Server’s XQuery and XPath capabilities.
• You want to optimize your queries of XML data using indexes and SQL Server’s query optimizer.
XML is a particularly good choice as munication format for loosely coupled systemsor when trying to make legacy municate with modern servers. It’s also an excellentchoice when storing data for applications that lend themselves to using data in a marked-upformat, such as document management and presentation applications. Modeling semistructured data in an ad hoc fashion also lends itself well to using XML. There are many standard applications for XML already defined in almost every industry, so XML is often an excellent choice when munication formats and data sharing are high , and when, to use XML is the subject of much debate among SQL Server are situations where XML is not the best tool for the job, including the following:
• Your data is highly structured and dense (non-sparse).
• Order is unimportant to your data.
• You do not want to query data based on its structure.
• Your data is best represented using entity references.
Additionally, if you do not intend to query or manipulate your XML data on SQL Server, but just want to store and retrieve it, you should use the varchar or nvarchar data types instead of