question

Dakro avatar image
Dakro asked

Shredding XML messages(not files) in C# vs. SQL Server

I know most like to shred XML messages in C# apps, but we have a massive comms platform, and any changes to XML messages requires changes in the comms platforms which leads to big testing cycle. in contrast, shredding XML in SQL has made our application quite agile to changes based on vendor requirements. However, the application is taking off and scalability will be an issue soon. I hear from some of my colleagues XML shredding in SQL is single threaded and is quite costly. what do you think will be faster and more efficient?
sql-server-2008-r2xml
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Grant Fritchey avatar image
Grant Fritchey answered
Faster and more efficient? C#. SQL Server can work with XML, but it's fairly memory intensive. If you do have to use it there, be sure you have plenty of memory for the processes. Monitor memory carefully. That's going to be your bottleneck.
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.