读取XML数据和构建查询以将值插入SQL Server数据库的最佳方法是什么？

Question

What's the best approach for reading in XML data and building a query to insert the values into a SQL Server DB?

Anyone have a best approach for this type of scenario?

Answer 1

Personally, I use a DataSet.ReadXML(). Then it places all the data into DataTables in the DataSet and then is much easier to loop through and manipulate the data.

Answer 2

SQL 2005 has very good xml capabilities. This is one technique using XML Parameters

Answer 3

Are you aware of the XML features of MS SQL Server 2005/8 ? You can insert XML strong typed directly as a column into SQL, and then enforce that the XML is valid against the specified schema.

You can even index columns within the XML and run Xquery against it.

Could we have some more information about what you want to do?

Answer 4

If you are after fairly simple data (ie the first-level children), then an option I've used successfully in the past is to use an XmlReader to read the xml (on child at a time), presenting the data in a lightweight IDataReader that SqlBulkCopy can consume to pump the data in. Like so . If the data is more complex, use sqlxml / bulk load.

Answer 5

编写一个与xml具有类似结构的数据库模式，然后编写一个Linq To Xml和Linq To Sql语句来推送数据。

Answer 6

Pass the data to a stored procedure as an XML document to an variable with the XML data type. Then parse the document within the procedure and load the data into a table.

I give examples here .

Answer 7

Your question is not clear on the details:

If you have arbitrary XML files you want to insert into a db table, declare an XML column (SQL2005+) and simply insert the data as string.

If you have XML files adhering to an XML schema, you can declare an XML SCHEMA COLLECTION using the XSD, bind the XML column to that xml schema collection, and insert the data. SQL Server will validate every inserted XML value against that XSD.

If you want to manually parse the XML data, use XPath or XPathNavigator or XMLDocument.SelectNodes to extract the data, and insert them record by becord into your db tables.

You probably want to be more specific in your question which of the alternatives apply to your case.