@dickersonka:
Thanks for sharing your idea. I am glad you understand what I am actually looking for.
The "translate()" function, as you wish to, works with Oracle, but MS SQL server does not have that inbuilt function. Instead, as I had said in my first post, it has a "replace()" function which works a bit differently.
Eg:
SELECT REPLACE('12345','123','');
Output
---------
45
SELECT REPLACE('123,'13','');
Output
---------
12345
So I am still on a lookout for something to work as we want.
@Geek-Master:
Yes, as you said, it is not good to fiddle with user inputs and you identified that sometimes business logic might ask for it(eg: Name field), I want my DB to be robust enough to resist faulty inputs if my API misses it by any chance or some other malicious reasons.
As you talked of CLR, then yes that can be done using CLR(that is the only thing I know about it

) but I am not sure how to. So I am trying to follow
MSDN's RegEx path and
an example on adding RegEx to the DB.
It would have made life easy if something like "translate()" would have been available. I am trying my best to find a way.
Thank You.
Regards,
HKansal