what best practices controlling thread internal storage .net?

i have requirement concentration i cruise met controlling thread internal storage, nonetheless i'm wondering it's those things that's best avoid.

i have review few articles subject:

i know how it, i'm only wondering i should it.

any advice, gotchas wakeful of?

[edit]

here's case:

i flue information opening by few methods lot logging any query. thing i record finish dump management calm commands filled i simply copy-paste snippet logs directly sql supervision studio.

way adult global.asax web apps i send email admins many information i i an unhandled exception. i wish put sql management dump calm email i sqlexception, save me digging by snippet logs page blows adult since query.

i don't wish change slight signatures information opening classes only i pass anxiety proceed down stack, only out i an exception. i pondering maybe tls good place put something "lastsqlcommand", nonetheless that's looking viable solution.