Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-12-16 : 19:27:07
|
| Eric writes "I am distributing an app that uses stored procedures. Is there anyway to keep my client from seeing my stored procedure's code on his server?I'm using SQL Server 7.0." |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2001-12-16 : 19:33:38
|
| HiIf you create your procs using the WITH ENCRYPTION option it won't be readable.If you do this, you NEED to keep all of your Create Procedure script files.Preferably in source control....backed up. We get lots of questions here "how do decrypt my procs, we don't have the source" and basically the answer is "tough"Look in books online for more about WITH ENCRYPTIONHope that helpsDamian |
 |
|
|
VyasKN
SQL Server MVP & SQLTeam MVY
313 Posts |
Posted - 2001-12-17 : 00:07:44
|
| Eric, if you don't want your client to see your T-SQL code, then don't ship your application using SQL scripts. Use Backup/Restore or detach/attach technique to ship your databases and make sure you create all your stored procedures, view, triggers, function with WITH ENCRYPTION clause.If you are not on SQL2K, then you will face problems with server code page. You can't backup/restore databases between different code pages. But you are fine as long as all your clients use the same code page. Or else you are gonna have to maintain different backup files for different code pages (Cumbersome...but works).This is not completely fool-proof too. SQL Server stored procedures can be decrypted. There are some tools/scripts out there that can do this.--HTH,VyasSQL Server FAQ, articles, code samples,best practices, interview questions and much more @http://vyaskn.tripod.com |
|
|
|
royv
Constraint Violating Yak Guru
455 Posts |
Posted - 2001-12-17 : 09:41:25
|
| Unfortuneatly with SQL 2000, they took away the ability to script encrypted stored procedures. You can still encrypt stored procedures, but you cannot script them out. Our solution was to have a SQL 7 Server here that we compile our code on, and script from that. Not a very elegeant and/or reliable solution, but our needs require the code to be encrypted*************************Just trying to get things done |
|
|
|
|
|
|
|
|
Protecting Stored Procedures