I am going to deploy a SQL Server-based application overseas. The question of
a "run-time only" version of SQL Server has come up. I don't have any
experience with "run-time only" versions of software. It was explained to me
that, for example, Access has this feature. It allows you to deploy the
database, but restricts users from being able to change things (I suppose
administrator-type things, like table columns, etc.) in the database. Use of
the database isn't restricted, however.
My situation is that I really don't want users to be able to modify my
SQL database, as this would make maintenance extremely difficult.
Does this ring a bell with anyone? Is it possible? Impossible? Maybe
even a silly question, since Access isn't on the same "level" as SQL
Server? Maybe there MUST be a local administrator (assuming that *I* am
not going to administer the server), and that this person MUST be trusted to
keep undesired changes from happening. I was just hoping to be able to
provide a more or less "shrink-wrapped" application that remote persons
couldn't alter. This may be impossible with SQL Server.
Any thoughts would be appreciated.