Hi Daniel
Thanks for answering
Sorry for poor english....just in UT no chinese

Even if encryption on data is also not a good solution, since M$ always suggested to use windows logon (trusted_connection='Yes')...a employee that not happy with a company may logon and do damage to all the data (update into sometable set somefield = 4%@#$@#$) ,thinks lost of 1 day transaction if doing backup. What Fabio suggested putting a inner password to DBO is a good idea.


>>Hi Sergey
>>Thanks for replying
>>
>>I'm asking help here...
>>That what i'm doing now ....encryping data...but that will
>>slow down speed in my software....and anyone can see the SP or UDF.
>>Seem to me SQL SERVER also not very good in security measures, should M$ ....
>>
>>
>
>SP's can be both be encrypted when created. Check out CREATE PROCEDURE and CREATE FUNCTION in the BOL.
>
>SQL Server is very good at security, as far as protecting the data from users. But there must be a level of trust between the developer and the client's DBA. You can't always be on site to fix their problems. And, as you pointed out, encrypting the data will cost performance. There is a trade off.
>
>Just my opinion.