Narayana Raghavendra


SQLServerCentral Article

Code Stored in Files Instead of Stored Procedures

This articles proposes storing the source code for stored procedures on disk rather than in the database itself, the intent to give developers the ability to easily change them or potentially to allow third party encryption of source code. (Note from SSC: If you choose to implement a technique like this, please be sure you understand the implications of exec'ing strings)

You rated this post out of 5. Change rating

2003-10-24

8,284 reads

Blogs

5 Advanced Online SQL DBA Training Courses to Learn in 2024 and Beyond

By

Buckle up, database wranglers! Nowadays, SQL DBAs hold the keys to a company's most...

Dynamically Unpivot columns in SQL

By

Picture this, your data ingestion team has created a table that has the sales...

Friday Basics: RPO and RTO

By

I did a post last month titled RTO and RPO are myths unless you've...

Read the latest Blogs

Forums

Azure SQL how to grant ALTER DATABASE permission

By Coriolan

  I have the user Managed identity <myusermanagedidentity> , granted it carte blanche alter...

Honeybee Swarms

By Ryan Booz

Comments posted to this topic are about the item Honeybee Swarms

SQL Server Encrypt data into a file, send it and then decrypt

By GBeezy

First off, my apologies for what could potentially be a bad title! I am...

Visit the forum

Question of the Day

Finding Marks

I have marked a few transactions in my code. How can I find out which marks were stored in a transaction log?

See possible answers