[dba-SQLServer] SQL Server Field Data Security

[Stuart McLachlan]

It depends on who maintains the SQL Server instance.
An SA will have full access to everything, so you need to prevent them from making a 
meaningful change to the data.

Do they have access to an accdb or are you locking it down to an accde?

If it's only accde, you can encrypt/decrypt a field in the database and validate when it opens.

If it's an accdb, it's a lot harder to protect your encryption/decrytion routine ( maybe consider 
creating and distributing a DLL with the applicatin that is called to validate the SQL Server 
data.)




On 5 Jun 2023 at 15:06, David Emerson wrote:

> Hi Listers,
> 
> 
> 
> I have a couple of fields that I would like inaccessible to the
> client's IT department that might have access to my SQL database. 
> They store data that is used internally by my Access application to
> determine whether the users should still be able to use the software.
> 
> 
> 
> I don't want to store the values in the access application itself as
> the unlocking of the software should only be done once and apply to
> all users (who will have their own copies of the FE).
> 
> 
> 
> My thought is that they would be in a separate table and I would
> prevent anyone with SA or administrator roles from being able to look
> at the table design and data (or at least not change the data) unless
> it is me (but how do I prevent Administrator users from changing the
> permissions?).
> 
> 
> 
> What is the best way of doing this?  Is there another method (similar
> to Access Database Properties) where I could store the data in another
> place in SQL instead?
> 
> 
> 
> Regards
> 
> 
> 
> David Emerson
> 
> Dalyn Software Ltd
> 
> Adelaide, Australia
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
> 
>