I have a rather complex solution, with a lot of business logic within the SQL Server database, located in stored procedures and views. As a "old school" data warehouse developer, I have created a n-tier architecture with layers for extract, transform and model(s) etc.
I have to install my solution and the corresponding database within a customer database infrastructure, as opposed to placing the database in a container with limited access by users, keeping my IP protected. I want to prevent the customer or any employee, from grabbing and reusing the solution components.
Is there a way to encrypt or otherwise hide the actual T-SQL within procedures and views, even for database owners and administrators?
I created a C# console application using Entity Framework, that simply executes hard-coded T-SQL statements, as replacement for the stored procedures and views, but this prevents me from handling database incremental deployments (CI/CD) as intended. But it might be the only way...