"we attempt to compress the table using this statement: sp_estimate_data_compression_savings ..." is wrong because the sp "sp_estimate_data_compression_savings" just is an "estimate" and it doesn't compress anything!

SPARSE is not a datatype but a property.

So, the correct answer is wrong!

SELECT * FROM sys.types

WHERE is_user_defined='0'

+1

I prefer to use "SET IMPLICIT_TRANSACTIONS ON"

Only one transaction on first I/O and one commit.

SET IMPLICIT_TRANSACTIONS ON

INSERT INTO tbl VALUES

( REPLICATE('a',5000) )

GO 100

COMMIT

GO

print @@trancount

Waiting for commiting all transactions, in reality, the table is empty for the other connections.

TomThomson (7/26/2016)

---

Interesting question, but rather badly put together - it could have been a good question if it had simply included a statement saying that the four statements are executed...

That's not true!

Trailing spaces are stored also in nvarchar e varchar datatype.

Compare and len function ignore trailing spaces.

It's not a bug and nor a feature.

The first database is stored in sys.databases with double blank.

As you know, the compare condition and len function don't matter of trailing spaces.

So,...

The answer is in the title.

I found this:

https://msdn.microsoft.com/en-us/library/ms141679.aspx

From BOL:

Truncations. A truncation is less serious than an error. A truncation generates results that might be usable or even desirable. You can elect to treat truncations as...

Very, but very interesting!

Thanks.

🙂

The second option is useless, but it also is correct.

SELECT @p = N'@m varchar(200)="event message", @d datetime=getdate(), @u varchar(10)="Steve" '

I.e. this code returns 1 despite @p is initialized with 1234.

declare...

Great Steve! 100% wrong.

+1

😉

JSON is a big power!