Databases
StackOverflow2013
Postsdbo
POQuicker way to loop through LINQ data
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POQuicker way to loop through LINQ data
    primarykey
    data
    text
    <p>I am writing code that pulls data from database tables and writes them to an XML file (to be picked up by another process). There are bout 60,000 records, and each record can have multiple entites, i.e. a member can have several contacts, each contact can have several phone numbers, etc. The entire process takes several hours, and I've narrowed down the slowness to the actual pull of the data (not writing the XML, or any data processing after it's pulled, etc.). I've tried the code two different ways, with similar results. First I leveraged LINQ queries and created all the elements in one statement:</p> <pre><code>Dim output = From m In dc.members Select New XElement("member", _ New XElement("id", m.member_id), _ New XElement("address", m.Address), _ New XElement("city", m.City), _ New XElement("state", m.State), _ New XElement("contacts", _ From c in m.contacts Select New XElement("contact", _ New XElement("contact_name", c.name), _ New XElemdnt("contact_address", c.address), _ ... </code></pre> <p>I thought it might be the creation of all the XElements that was slowing it down, so I tried writing the elements directly to the XML file using For loops:</p> <pre><code>Dim output As New Xml.XmlTextWriter("my.xml", Nothing) For Each m in dc.members output.WriteStartElement("member") output.WriteElementString("id", m.member_id) output.WriteElementString("address", m.Address) output.WriteElementString("city", m.City) output.WriteElementString("state", m.State) output.WriteStartElement("contacts") For Each c in m.contacts output.WriteStartElement("contact") output.WriteElementString("contract_name", m.name) output.WriteElementString("contract_address", m.address) .... </code></pre> <p>That produced almost no change in amount of time the process took. I then tried stripping out all the elements and reduced the code down to just the database pulls, and it was similarly slow.</p> <p>Is there a faster/better way to pull all this normalized data from the database so I can get it to the XML file as quickly as possible?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USgfrizzle
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POQuicker way to loop through LINQ data
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POQuicker way to loop through LINQ data
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POQuicker way to loop through LINQ data
      1. USjohnny g
      1. VTFavorite
    1. COTechnically, you can have SQL Server (if that's what you're using) emit XML. But first you say you have "narrowed down the slowness to the actual pull of the data", then you provide two code examples of how you did exactly not that. Are you sure the pull is the problem?
      singulars
      1. POQuicker way to loop through LINQ data
      1. USbzlm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload