Are you expect row 1 to have the same value in both columns, row 2 to have the same value for both columns, row 3 to have...? That's not what...

What do you actually mean by this? SQL Server can tell you what user and login is being used in the current session by using CURRENT_USER() and SYSTEM_USER() respectively.

Alternatively, instead of using a Table-type parameter, you could consider passing the value as a delimited string and then using a string splitter.

Either way, Gail is completely right;...

The error message is quite clear here: "Transparent Data Encryption is not available in the the edition of this SQL Server instance." Emphasis mine.

As per the Supported Features...

Yes, you with the following
[Code]SET ANSI_WARNINGS OFF;

--INSERT  operation

SET ANSI_WARNINGS ON;[/code]
It's important to remember to switch the warnings back on afterwards.

Personally, however, rather...

You'll need to use an INSTEAD OF trigger. For example:

USE Sandbox;
GO

CREATE TABLE Table1 (ID int, String varchar(10));
CREATE TABLE Table2 (ID int, String varchar(10));

I'm thinking, Phil, this is likely due to our good old friend Mr "Double Hop". If the OP is having issues running it using SSMS, but can do so fine...

It is there: https://support.microsoft.com/en-mt/hotfix/kbhotfix?kbnum=967909&kbln=en-US

Make sure you click "Show hotfixes for all platforms and languages".