TDE does not meet those requirements. It may be part of meeting them or it may not, but it's not sufficient. It also doesn't stop someone from querying the data...

It's SQL Server waiting for the client to accept the results and send an acknowledgement. It's usually the client app, but could be anything from the server to the client...

Michael Valentine Jones (1/16/2014)

---

TDE will protect from two main threats:

Using the database backup files to restore somewhere else and looking at the data.

Copying the database data files, attaching to another...

From what? What threats is this going to mitigate?

TDE isn't a general 'protect the data', it protects the data from specific...

They are, they always have been. Drop a temp table and you can't access it any longer. Essential when testing code before...

To solve what problem?

SELECT database_id, object_id, index_id, avg_fragmentation_in_percent FROM sys.dm_db_index_physical_stats(9,933578364,5,null, 'limited')

SELECT DB_NAME(9)

SELECT object_name(933578364,9)

What do those return?

You told...

Prerequisites including reading up on how you restore...

Shouldn't be noticeable.

Repeat that code for each temporary table. Or just close the connection

Yes, it encrypts TempDB as well. The log is part of the database so 'encrypts the database' means encrypts the data files and log file.

Then all I can suggest is double check that you are looking at the correct server, correct database and correct query. Most common reason I've seen for problems like this...

As in, from the database you're in, querying FROM sys.indexes where object_id = 933578364?

Is the database you're currently using the one with an ID of 5? The sys.indexes view is...

How are you checking the index defs in database 5? What query?