Decrypt encrypted stored procedures

This stored procedure will decrypt stored procedures, views or triggers that were encrypted using "with encryption". It is adapted from a script by Joseph Gama and ShoeBoy. There are two versions: one for SP's only and the other one for SP's, triggers and views. For version 1, the input is object name (stored procedure, view or trigger), and for version 2, the input is object name (stored procedure, view or trigger), object type ('T'-trigger, 'P'-stored procedure or 'V'-view). From PlanetSourceCode.com.

Reader Feedback

Joakim M. writes: I tried this script with mixed results. It works for some encr

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Microsoft SQL Server Using the Visual Studio 2005 DataSet Designer to build a data access layer The CTE, the hierarchical query and SQL Server 2005 SQL Server 2005 recursive functions and the CTE Choose the right .NET data provider, optimize application performance The fallacy of the data layer -- or, a new architectural model for software designs Book excerpt: ADO.NET and SQL Server 2005 Addressing common SQL Server questions Book Excerpt: The .NET Framework and SQL Server 2005 WinForms development using SQL Server 2005 and Visual Basic 2005 Configuring ASP.NET 2.0 apps to SQL Server 2005 databases

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

ypted procedures, but for others I get error meassages like:

Karl C writes: I got the same message as Joakim M. but upon further investigation I found that this happens only when stored procedures exceed 4000 characters. When this happens, SQL Server stores the procedure across multiple rows so you get the error 'subquery returne more than 1 row'. To get around that you can change the statement

That will get you the first part of the stored procedure, which can't be created because it is missing the end part and is not a valid syntax but you can print @resultsp out to see it.

For More Information