Honestly, a little excited to go vote for "this page is full of hooie"...

#2. because it's probably just something the authors at Microsoft didn't put in as usual terminology (low value change, may not have been a concept they even considered). You could...

https://www.sqlshack.com/importexport-json-data-using-sql-server-2016/

Check out https://www.sqlservercentral.com/stairways/stairway-to-xml, that should get you started.

You're going to have to find the data. If you're running this on a regular basis to move stuff in, check this out:

https://www.sqlservercentral.com/articles/conditional-set-based-processing-moving-towards-a-best-practice-for-etl

uses Try/Catch blocks, you can attempt everything...

Add in WHERE tp.Field1 LIKE '%.%' and you won't have any errors. Won't parse anything either, but that wouldn't happen anyway.

You know what, is there a timestamp on when the process ran on that table? createdate or something? you could just set up the notification email to run on a...

https://www.sqlservercentral.com/articles/tally-oh-an-improved-sql-8k-%e2%80%9ccsv-splitter%e2%80%9d-function

might seem like overkill for the question you posed, but trust me, you'll use it many times, it's worth borrowing from Jeff et al.

If you have ErrorCreated, then you have to store what the message is separately. If you use the presence or absence of a message in ErrorMessage, then you know what...

Either that or create a stored procedure / trigger that decrements Quantity on Hand when an order is "processed" (so that the parts for it are reserved).  but that seems...

If you're wanting to know for an ongoing stream of orders whether you have enough parts to fulfill at any point in time, then you'd have to either use your...

I was thinking of our recent exchange with someone that multiple of us considered spam, but you did not because you were familiar with their posting style

Probably >3 within a timeframe, to be fair? not >3 ever?

We can't see your data, but try the following:

1 - just return the charindex() and len() functions as separate fields, so you can see what the calculations are that are...

I have never understood the utility of returning the bit value from a stored procedure execution. It's too abstract of a concept to say "it worked" or "it didn't work"...