Do too many number of attributes affect performance badly?

[hk yoon]

Hi,

I'm trying to load xml file into ASP.net.
The xml is dictionary type of file and so has many attributes and subelements.
Current size of the xml file is about 1MB.

Now, when I try to load the xml file in ASP with native server controls - like XML data source and Grid View, although this is not what I want to do eventually, the build time costs more than 30 minutes.

(1) Do you think this long build time is due to the number of attributes? I'm asking as I think I read somewhere that the attribute should be used only for meta data, and recommends to get those attributes to (sub)elements as much as possible.

(2) As for the MS's .net side: There seem to be many competing technologies about handling xml files in .net framework. Things confusing me are:
- ADO.net
- SQL Server's column native format xml files
- .net 3.5's LINQ
Also, there are many query languages for handling xml like:
- native XQuery
- SQL after converting into RDB tables (XQuery embedded in (or wrapped in) SQL)
- LINQ query

As said, I'm trying to load xml file for a kind of dictionary, and provide web access to those visiting to my home page. I still think loading xml files in its native format should be most flexible in providing new applications in future.

Any comments or recommendations?

Thanks in advance.