Views on Using XML as a Proc Stored Parameter and Return Type

Question

This is new to me. I have a new boss at work who insists that every request we make now is a sproc with XML serialized parameters and return types.

I haven't run any tests yet, but it hits me like an excess and possibly a performance killer in many ways. What is your experience?

Answer 1

Although it is an obvious performance killer (imagine that parsing a few megabytes of XML is coming back from sproc), it further enhances performance, scalability, and a killer for performance. Working with XML in T-SQL is not entirely painless or seamless. Support will be a nightmare: imagine adding one column to the result set, which will lead to an avalanche of modifications to the serialization and deserialization code.

In addition, you cannot use either ORM tools or simple graphical agents (iBATIS or BLToolkit).

Answer 2

( proc ), , .

, .

Answer 3

, ; -p

, . Xml , TDS (.. ) . CSV (split by udf), (SQL 2008).

Sql/xml 2005+ , openxml - , , , xml ( xml), , , .

, .

Answer 4

, , , . // Xml, , SProc , . - - ...

, ?

Answer 5

(: messy) , , , .

- , . - , , , XML . , , , XML , : , XML , , TDD .

, - , : "XML , ?" , .

Answer 6

. SQL - ., xml? (, , procs)

, procs, , xml. , "" .

Answer 7

, : .

XML - , : , , (, ) .

, , , . XML .

, ( ) , . XML , , , . . .

, , , , . , , , . , , XML.

, , ? , , ?

, , , XML Everywhere , . , , , , , , , , . , , , .

Answer 8

(Browser) -. , ​​ -. XML , - , HTML. XML - -, , -, .