StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4395524
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-12-09T06:33:03.117
FavoriteCount
0
LastActivityDate
2010-12-09T06:33:03.117
LastEditDate
LastEditorUserId
0
OwnerUserId
13302
ParentId
4394278
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The only viable approach I see is trying to do this: <ul> <li>parse/shred your XML arrays into temporary tables for phones and addresses</li> <li>those temporary tables have an <code>ID INT IDENTITY</code> defined</li> <li>when inserting into a fresh temporary table with this INT IDENTITY, both sets of data will get consecutive numbering (1, 2, 3, 4......) </li> <li>you can then join the two temporary tables on their ID and should get your "lock-step" behavior:</li> </ul> So in code, this would look something like (mind you: your XML is invalid, too - the attribute values need to be in double quotes for this to work!): <pre><code>DECLARE @phones XML = '<PhoneID Value="128"/><PhoneID Value="129"/><PhoneID Value="130"/>' DECLARE @Addresses XML = '<AddressID Value="268"/><AddressID Value="157"/><AddressID Value="395"/>' DECLARE @phoneTable TABLE (ID INT IDENTITY PRIMARY KEY, PhoneID INT) DECLARE @AddressTable TABLE (ID INT IDENTITY PRIMARY KEY, AddressID INT) INSERT INTO @phoneTable(PhoneID) SELECT PHID.value('(@Value)', 'int') FROM @phones.nodes('/PhoneID') AS PH(PHID) INSERT INTO @AddressTable(AddressID) SELECT ADRID.value('(@Value)', 'int') FROM @addresses.nodes('/AddressID') AS AD(ADRID) SELECT p.*, a.* FROM @phoneTable p INNER JOIN @addresstable a ON p.ID = a.ID </code></pre> Does that work for you?? From here, you could then insert the data into your actual working tables and do any additional lookups or processing.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POparsing multiple xml arrays in sql
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmarc_s
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COI'm not 100% certain that it's guaranteed that the IDENTITY values will match the "insertion" order, unless there's an ORDER BY clause in the `INSERT...SELECT` query. It may appear to work for small samples, and fail with larger queries
 singulars
 PostPostId
 PO
 UserUserId
 USDamien_The_Unbeliever
2. CO@Damien_the_unbeliever: yes, I agree - it's a bit "risky", but if there's nothing else to go on.... if you create new table variables, they're empty, and the ID will start at 1 for both - that's about as good as it gets without any better "handle" to tie the two parts together...
 singulars
 PostPostId
 PO
 UserUserId
 USmarc_s

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.