Just to share what I have figured out so far, here are the nodes or paths that have the metadata I want and the .value paths as well.

...

Thanks. I have been working parsing the XML that is in ReportCatalog.Content, but I was just hoping someone else had already done this. More importantly, I don't want...

I would agree about creating a new thread. However, if your problem is as simple as your question, then the following SQL, or something like it, should suffice to...

Kudos to whomever allowed me to subscribe to a topic and get an email. 🙂

It looks like I forgot to add the dynamic SQL that puts all these pieces together.

-- Piece together everything into a single dynamic INSERT statement

...

And for whatever reason, when I try to use the sys.dm_exec_requests table, I do not get the expected results. I try the following code and I get...

Thanks, Kent. I never heard of the Context stuff before, so that was very helpful. It still acts as a way of tracking things across procedures, without passing...

How can I see the contents of the TXT files? When I click on the link to the TXT files, I get a SQL Server Central page with the...

The UNION ALL and EXCEPT method will work and is easier to understand, but it is too time consuming for me. If you use 'select *' with the...

Not sure of the output you want. For a list of people that have been added...

select ID from Phone2

EXCEPT

select ID from Phone1

An alternate method could be used and...

select PersonId, count(PersonId), (count(PersonId)- count(Value+AltValue)) as CountNulls

The (Value + AltValue) will result in a null if either is null

Change the SELECT to ...

SELECT @List = COALESCE(@List + ',', '') + '''' + Cast(somedata As varchar(5)) + ''''

PS. I never knew COALESCE could be used like this to...

There may be a more elegant solution for the nulls, but this should work

select PersonId, count(PersonId), (count(PersonId)- count(Value)) as CountNulls

from dbo.Table_1

group by PersonId

Just for completeness, here is the revised code for parsing out the old ane new values into the final table...

IF UPPER(@p_details) = 'YES'

...

Ok, I could not let the lack of old and new values wait any longer. Here is the revised code that accounts for whether the old and new values...