Wait a minute, Jeff!

You suggest to "simply" add a FROM clause to the update statement? (The alias isn't mandatory, is it?)

Interesting, what kind of "previous experience" you can refer...

I can't reproduce the scenario you described.

Based on your sample data the code runs as expected (I'm purposely not saying it runs "fine" 😉 ).

If you already tried several filters...

Can you provide a test scenarion so we can reproduce it on our machines?

I'm confident the c.u.r.s.o.r. *cough* doesn't restart "all of a sudden, all by itself".

My guess would be...

You must not be any specific permission for this user (or role) for Schema A. Otherwise the "least privilege" concept would apply and you might not be able to call...

You'll need to make sure that the owner of both schemas and the sprocs being referenced is the same (e.g. 'dbo'). Then you don't have to do anything special other...

The best solution would be to get rid of c.u.r.s.o.r. *cough* in the first place.

Insert all data into lpn at once and use the OUTPUT clause to get the returned...

You would need to setup a server side trace (runs without the profiler User Interface being required, look up "sql server side trace"). Otherwise there'll be quite some overhead, even...

Let me repeat what I posted before. SSMS has no option out of the box.

As much as you request it, if the software doesn't have this option, it doesn't help...

If you can't change the designe then you'll need to apply the same concept using subqueries (or cte's).

You've already described the WHERE condition of the two subqueries involved. All...

There's a duplicate reference to the abc_NODE node in your node reference

('(abcS/abc[@NAME="XXX"])[1]/abc_NODE[1]//abc_NODE/AVAL') AS X(c)) should be

('(abcS/abc[@NAME="XXX"])[1]/abc_NODE[1]/AVAL') AS X(c))

Export the data from Quickbook (e.g. as formatted txt files) and use SSIS to read the folder and import the data.

If you don't want to use SSIS , you could...

Since you already have the BorrowerOrder column I'm not sure why it would need to be so complicated...

Wouldn't a simple BorrowerOrder < 2 be enough?

SELECT

*

FROM

#t AS t

WHERE BorrowerOrder <...

You might want to ask this in an Oracle forum.

The question is related to the source (Oracle) and not to the target (SSIS or SQL Server).

Anyhow, the solution won't be...

The solution is easy: it's called "Normalization"!

Move the column [Inventory] to a separate table with a reference to [Item] and move the rows with non-blank values.

Then it's just a simple...

There are Add-Ons available that provide the option of a "query history". Tools like SQL Prompt (Red Gate) or SSMSBoost (Solutions Crew).

You'd need to find the folder where this information...