Thanks for all your feedback.  I intend to use all these comments to better not only my understanding on this topic, but also further articles.  Most of my work revolves...

Absolutely, Mr. Strange.  The obstacle of "complete" code.  My best approach is to have a talk about code standards within your organization to develop guidelines before-hand.  My approaches to any...

Thanks for your response, David.  You are absolutely right that a single query is not *always* better performance-wise than other queries, because the execution plan can surprise you.  Without knowing...

Thanks for all your replies everyone.  I was hoping to see other experiences too--I can't be the only one who worked at companies like this.  I'm happy to say my...

Thanks for your help.  Before I burn you both out, let me do some more research and wrap my head around the keys and how they're related to TDE.  Though...

Thank you both, Sue and Perry.  I appreciate your patience with me.  I'm working through the articles provided, as well as the Microsoft article on TDE and keys/certificates.
One final...

Thank you for your feedback.  Yes, I am planning on implementing TDE.
What I'm hearing is that even though I do not know the original password for the SMK, as...

ZZ,

Thank you for your feedback about web front-end. I don't like C# because I feel it would lock our organization into an MS-only shop; but I'm not a skilled...

Hi Steve,

In my brevity, I think I left some details out. I don't believe this will be a case of users editing their reports--they'll input other data that will...

I thought of that too, and I think some of the hesitance of using it comes from the problem getting unmanageable. I would consider two select statements if I...

That confirms it. In my code, I'll steer the work toward dynamic sql whenever I can. Thanks for all your help.

Nice to hear the question is asked in many other places. Your post was well-researched, and adds another solution: dynamic SQL. It also stresses the importance of a...