>>I need to pass the object to SQL procedure. I think it's easier to pass as XML. I would have used table variable, but we're still supporting SQL 2005 thus I am using XML as my SQL procedure parameter.
>
>What difference does that make? It's just strings you're passing either way unless you're explicitly using the SQL Server XML types (which are a pain to use anyway)...
>
>Either way it's pretty trivial to create a wrapper routine for either XML or Json that you can call easily from your application.
>

I am using XML type in SQL Server procedure to get that object and parse back into the table.