Don't want to give stored proc to client?

[THY02K]

Don't want to give stored proc to client? What are your options if there is one?

Thanks

[Shuja Ali]

None as far as I know. Why is it that you don't want to give it to the client?

You could probably write .NET code to replace the logic that is in the stored procedure.

[ComITSolutions]

If you are using Sql Server 2000. You can create the stored Procedure WITH ENCRYPTION option.
But Once stored procedure created with this option you can not edit, so before creating sp with encryption, keep a copy of stored procedure in a file for later reference.

[THY02K]

Shuja Ali > Why is it that you don't want to give it to the client?

Because I'd don't like to hand over the source, others to copy and would like to charge money for my product.

[Alsvha]

Why would you have to give the sproc to the client then?
Have they asked for it? If so - have you signed a contract which says they should have it - or something?

If it is so they can call the sproc, just provide the name and the parameters they should use. They don't need the actual implementation for that.

[Shuja Ali]

Shuja Ali > Why is it that you don't want to give it to the client?

Because I'd don't like to hand over the source, others to copy and would like to charge money for my product.
Then instead of writing the logic in a stored procedure, write it in your code (whichever language you are using). By the way, who said people can use the stored procedure, does every one have access to the SQL Server that your client is using?

[THY02K]

seems like SQL server is the only database with "WITH ENCRYPTION" option.

anyway, i have some code in sql because it'd be most optimized there. And the rest in application layer. Just looking around to see if I've missed anything.