Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have to shred the xml contents (transaction xml ) into some 7 tables. The approaches i’d in mind is
a) Single SP, use OPENXML and traverse through the xml contents and update the required tables.
b) Load xml in Xdoc and make a entity objects and update the required tables.
XML is big in size and has around 1000+ nodes.
Which is the best approach of the above two?
SQL Server has had XQuery since version 2005. That’s the preferred way to work with XML nowadays and has been for a long time.
OpenXML has many limitations and issues, one of the biggest is the possibility of memory leaks when you don’t dispose of the handle properly.
Just picking on one StackOverflow sample question and one Google result: