SQL Server Performance

XML performance

Discussion in 'ALL SQL SERVER QUESTIONS' started by jim123456789, Apr 20, 2013.

  1. jim123456789 New Member


    We are using FOR XML which is causing a huge performance issue. Could you please suggest a better approach? Also, it would of great help if you give a general guidance on performance on handling XML. For eg, we are using XML.Node(), XML.Value(), Convert(XML to string or vice versa). Please suggest is it a good approach to use this from performance point of view.


  2. Shehap MVP, MCTS, MCITP SQL Server

    First, welcome to forums …

    Usually XML performance is going badly unless you create a primary XML index at least , but I get afraid about the DB size coz rapid inflation of the size can happen due to XML index size but what I can say here that of your XML column is heavily selected for searches , it is much better to dispose XML column and replace it by flat columns having flat data types like varchar (n), float , int …etc to enjoy efficently with indexing feature with no impact on DB size and storage capacity as well ,but if your XML data is used for limited search or its volume is acceptable then XML option is more granular

    Kindly let me know if any further help is needed

Share This Page