Hi Joe,

thanks for the excellent feedback! I can see now that I should have structured the article a bit differently to make it clearer.

Regarding the built-in security, I'd like to...

Hi al-243208,

I think the right way to think about this is to compare it to the alternative. If you need fine-grained access control for your stored procedures, the first thing...

Well, ultimately, Microsoft is a business, and a business needs to make money. We all have to make trade-offs. It's just that this particular trade-off seems short-sighted. It's the kind...

Hi jshell687, thank you for the feedback! It sounds like you are more experienced than I am in the practical use of linked servers, so I defer to your superior...

Ken writes:

Do you think it would be possible to point an old application at the proxy and get it to query a different db than what it was designed for...

• This reply was modified 2 years, 11 months ago by  maxtardiveau.
• This reply was modified 2 years, 11 months ago by  maxtardiveau.

I might quibble a bit with "non-enforceable as a standardized approach" -- if you access the database through Gallium Data, you don't have a choice, the data will be masked...

> why not use SQL Server data masking by keeping it simple

And if that works for you, then yes, absolutely -- why would you use anything else? Gallium Data comes...

Hi Eric,

I think the arguments for SQL Server's row-level security are:

1. it allows you to control access to your data without changing your schema
2. it is specifically for access control,...