July 30, 2010
Login
|
Home
FAQs
SQL Server FAQ
SQL Injection FAQ
SQL Security Checklist
SQL Server-Related Products
SQL Server/MSDE-Based Applications
SQL Server Version Database
Tools
Lockdown Script
Free Tools
Free Analysis
Group Policy Templates
Commercial Tools
Community
Discussions
Links
About
Search
SQL Security Forums
Note: SQLSecurity.com does not allow nor require registration due to privacy concerns for users. SQLSecurity.com is open and anonymous for all. Please report any abuse or profanity.
Unanswered
Active Topics
Forums
Search
UserName:
Subject:
Protecting my design
Body:
[quote]Posted By n/a on 01/01/2001 12:00 AM I would forget about trying to hide your design. If the code is running on their servers then they can reverse engineer anything you put on it - even your compiled VB code. The tools already exist to do this. I would concentrate on making sure you get good lawyers and make sure your code contains the necessary disclaimers. You could stop some casual theft by encrypting your stored procedures (using the WITH ENCRYPTION option) but your tables will always be visible to the sysadmin role or the 'sa' account. The customer will need this level of privilege to maintain/backup/optimize/repair the SQL Server - it is THEIR server after all isn't it? Chip [/quote]
Show Replies:
ActiveForums 3.6
Copyright 1999 by Chip Andrews
|
Privacy Statement
|
Terms Of Use