Home/ Questions/Q 8919163
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T05:56:48+00:00

I have inherited some programming duties from my coleagues(<-spelling), with which I am given

  • 0

I have inherited some programming duties from my coleagues(<-spelling), with which I am given a users table structured as such:

userID BigInt (1,1)
Username Nvarchar(100)
UserPass Nvarchar(100)
Profile  Nvarchar(max)

They have programmed all logic for the username/password, and the client went back to them and stated “We now want user profiles”. Since the client already has control of the db, we are not allowed to mmodify existing storage objects, however, they did give us the new Profile field.

What I am wondering is this:
What would be better for performance…? Are there any benchmarks anywhere?

A)Storing profile data as XML
B)Storing profile data as JSON
C)Storing profile data as a comma-delimited list
D)Other that I have not thought of...maybe store a XML file in the filesystem tied to the userID?

for any of the above, I will be typing out and breaking out into objects. Personally I would say JSON, and I can utilize the JSON.Net library

p.s. This will be in .Net 4, and SQL 2008 R2 on a Win2k8 R2 server (that is personally theirs, and very powerful)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think that both XML And Json are acceptable in this case seen as you are forced to store the profile this way.

    I have used XML in the past for this mainly for the structure and readability when looking for related profile properties.

    if you are worried about the size of this (id imagine it would be quite small though), store the xml in a compressed state.

    • 0