Thanks for the interesting question Mohammad. Query result is better seen from this auxiliary script:

DECLARE @emp TABLE ( id INT );

INSERT INTO @emp VALUES ( 1 ),( 2 ),( NULL...

Thank you for your useful question and good explanation. A similar instructive example

is shown in this ref: https://msdn.microsoft.com/en-us/library/ms188048.aspx

Interesting question, thanks for excellent explanation and comprehensive reference.

An interesting question, which can be interpreted differently, thanks. It is quite unfortunate

that even this piece isn't critical to the puzzle https://support.microsoft.com/en-us/kb/926070%5B/url%5D

Thank you Uwe for this interesting question, very good explanation and the links.

I learned today something new.:-)

A really interesting question , thanks Umer . But just simple complicated? 😉

DECLARE

@max-2 AS NVARCHAR(MAX) = ''

, @Var AS VARCHAR(4000) = 'ABCabc123';-- Varchar instead Nvarchar --

SET...

Useful and interesting question, thank you Steve.

The same result for i may give also this script:

SELECT

MyID

, COUNT(*) OVER (PARTITION BY '') AS i

-- OVER (PARTITION BY '') is the same...

Interesting question, thank you Steve. It reminded me of these two interesting links:

https://sqlserverperformance.wordpress.com/2009/10/29/suggested-max-memory-settings-for-sql-server-20052008/ and

http://www.sqlbadpractices.com/keeping-maximum-server-memory-default-value/

After all, just something new today for me, thank you Steve. Happy New year to you all.:-)

Marry Christmas and thanks for your work on the SSC.com, Steve.:-)

Jiri Vobr, Czech Republic.

Thanks Steve, may could help also this reference: https://msdn.microsoft.com/en-us/library/ms190806.aspx

Very interesting topic, thank you Dathuraj. Outside references to MSDN, i used this article:

http://blogs.sqlsentry.com/aaronbertrand/t-sql-tuesday-69-always-encrypted-limitations/

A really interesting question. It gave me a hard time :crazy:, but it was worth it. I learned something new and I got it right 🙂

It was unnecessary " to...

Again, a well-refined questions, thanks Hugo .. I had burned on statement X.:crying:

Residual Predicate is well explained in:

https://www.simple-talk.com/sql/learn-sql-server/showplan-operator-of-the-week---merge-join/

Is this modification of your original code a nudge in the right direction?

DECLARE c1 CURSOR READ_ONLY

FOR

SELECT order_no FROM shipping_data

DECLARE @ORDERID char(15),

@myLen Int,

@Result CHAR(3)-- Modification 1 --

OPEN c1

FETCH NEXT FROM c1

INTO...