OK. I was wrong, very wrong. But thankfully, I met this website and all of you -wise and highly experienced pros -who let me know the truth and the truth...

really ? 😉 you did see it ? you have used it ? you know exactly how much money it already bring to...

DBAs have very little to do with the buy or not to buy decisions in the real world. Competitive design and price and - that's what's all about.

Yes. I think that SQL server should be used for fast and consistent data access but final processing is job for CLR.

And what would you advise to us? To serve to all the competitors de-facto source code on golden plate and share with them results of years of research and development...

Yes, but at least key parts can be hidden in armored CLR.

I am right ?

Right, anything can be taken under reversal engineering, even native (push ebp - mov ebp, esp - mov eax, 10h -... I do know a bit about it :-)) but...

You can use reflector and you will get only rubbish. There are ways how to deal with Reflector.

Stopping thieves this way is not ideal, I do agree, but it is better than let them steal your work. Btw, deploy clr is one way process so maintenance aspects...

You are right, just CLR is NOT a way, but I can prepare CLR code obfuscated such a way that it would take ages to rewrite it into readable form,...

tempdb is dynamically created and always copy collation of the mater db. Temporary tables are stored in tempdb. So if your db has different collation than master db has...

CLR seems to be a way, nevertheless debugger still displays SQL commands. Any way to stop it ?

Yes, of course, but this is very weak protection, dozens of decryption tools can be downloaded. I mean somenthing stronger like the "Shield" but preferably not 3rd party product.

This is usually conflict tempdb x yourdb, so rewrite stored procedures and add collate database_default. You can, however, try alter table alter column and unify collation