c# - Mangling column names in MSSQL for security -

i joined new project previous product manager decided mangle column names in majority of tables, hear aimed @ security/protection of our code since major part sql stored procedures.

here's simple visualization:

+-----------+------------+----+----------+-------+ | c1        | c2         | c3 | c4       | c5    | +-----------+------------+----+----------+-------+ | john doe  | 11-11-1944 | m  | street 1 | julie | +-----------+------------+----+----------+-------+ | mary jane | 13-02-1991 | f  | street 2 | null  | +-----------+------------+----+----------+-------+ 

somewhere agree him need mangle names, not when developing rather before delivering product customer. application in .net c#.

first, how can recover this? strategy or preferably tool (similar lines of uglify js)?

second, how can still protect code (stored procedure) after unmangling names?

i have no idea why think mangling names make system more secure. if want security, use database security features. instance, don't allow read tables directly, require stored procedures used. or, encrypt data itself, doesn't read. normally, data secure, not names of columns.

that said, don't see how can away "mangled" names during development. could use views map mangled names unmangled names. however, means have bunch of code needs changed when database structure changes. worse, means original developers confused when trying solve problems after release.