I was able to do hardcode the column and transpose rows to column; however, couldn't do it dynamically... will keep trying.

Thanks bt for your response... I will take a look at those.

You want the user that should be able to select the data using (the SP) from front-end but not be able to view decrypted data and view nulls instead rite?

Laura...

Laura how about creating a View?

If the users who do not have access to Select Procs that decrypts the data do a select using Query Analyzer, they should not be...

Only grant access to the symetric keys to those users/roles that absolutely need to decrypt any column.

Grant execute only on the stored procedures that are required to retrieve specific...

Thanks a lot for your response.

try this laura:

http://sqlserverpedia.com/blog/sql-server-bloggers/sql-server-encryption-for-express-or-standard/

when you load the data or when application loads the data you would know what language correct.. Use that for the new col and when querying they can use that...

Optimize the query and u should be fine. Do not use cast, trimming, substring, order if u dnt need to.

may be he is dynamically creating the table and using that table for other steps...

or add another column which will have code for language like 1 for english...

CREATE PROC ...

AS

BEGIN

DECLARE @strSQL varchar(4000)

SET @strSQL = 'CREATE TRIGGER....'

exec (@strSQL)

END

WITH my_cte

AS (SELECT fruit,

location,

...

http://www.mssqltips.com/tip.asp?tip=1405

Check this...

Did you create the Environmental Variable?