I thought of using application roles in SQL Server and encrypting the login info in the app.config file.
The problem with that is that once I install the database on the client's instance of the SQL Server, he gets administrative privileges.
Is there a way around this?
The real question is why would you want to do this? I have never seen a situation in which a database schema alone—with no data or business logic—would provide any value. The value is in what you do with the data (or what your application does). If you must guard your metadata, I don't think SQL Server is the database management system for you. You should look into implementing an embedded database management system or building your own proprietary data persistence system.
Do you have comments on this Ask the Expert Q&A? Let us know.
Dig Deeper on Microsoft SQL Server 2005
Related Q&A from Adam Machanic
Migrating to SQL Server 2005 from SQL Server 2000 is a hefty feat when compared to upgrading from 7.0 to SQL Server 2000. Site expert Adam Machanic ... Continue Reading
Multiple readers can sometimes read the same row simultaneously causing a false result. SQL Server 2005 expert Adam Machanic suggests modifying the ... Continue Reading
SQL Server 2005 and T-SQL do have differences. The advantages and disadvantages would depend user environment as described by SQL Server 2005 expert... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.