Yes, this is the exact usage case for a FULL OUTER JOIN:

SELECT 
    COALESCE(t1.PhoneNbr, t2.PhoneNbr) AS PhoneNbr,
    COALESCE(t1.Interval, t2.Interval) AS Interval,
...

Yes, the DIFF will.  You can do a DIFF any number of days after a FULL and it should work fine.  If a lot has changed in the db, the...

Agreed overall.  I will say, I wouldn't object to providing the user with a view ("table" perhaps to them) that had 600 columns, if that is what they needed.  But...

If you're directly designing "tables", you don't have a good design process and you are not doing proper normalization.  That's because normalization is a logical process, not a physical one.

What...

To save space, ENCRYPT the body (and other very long columns).  This process is rather slow, but it typically does save a lot of space.

And, using triggers, you...

What a mess!

(1) as above

(2) yes; you might consider breaking those links until after you're cleaned this up.  Then again, that has its own issues as well.  What a mess!

And...

To save space, COMPRESS the body (and other very long columns).  This process is rather slow, but it typically does save a lot of space.

And, using triggers, you can make...

It's more likely a bug in the app.  When it gets the result set from the temp table, what does the app do with it?

Is it possible to exit the proc without falling thru to the DROP TABLE? What about the start of the proc? If the temp table already exists,...

Is it possible to exit the proc without falling thru to the DROP TABLE? What about the start of the proc? If the temp table already exists, does...

I can't see how presence of existing TEMP table would cause a problem as

CREATE TABLE #ReportResults (dateStamp dateTime NOT NULL, dataInterval int)

would then fail.

longshot : But ... maybe it...

I don't think I'd blame this on...

So why did you just re-ask the exact same q?? Via q "Appttime add with duration how to get endtime please".

Duplicate q.  See q "Please help to get duration between two 4 or 3 character string" in this same thread.

A MERGE join requires input data sets that are sorted in the same order.  SQL decided it was better to sort one (or more) of the input sets so that...