You can set the database to be read only, but that may not work. If you intend to run the old application to reference data in the database, then you
may run in to problems with this. You see, the old application may write data to a table to log logins, or other changes. If you set the database to read only, you may not be able to log in with the old application.
To set a database to read-only....
Code:
Alter Database [!]YourDatabaseName[/!] Set READ_ONLY
To change it back...
Code:
Alter Database [!]YourDatabaseName[/!] Set READ_WRITE
I would suggest that you set the database to read only and then attempt to log in to it from the old application. If it works, then great, problem solved. If not, then you'll need to think of something else.
Restricting access to your users at the user level may be a bit problematic because it may be easy to "miss" something. I think you should do this (if necessary) but I also think you shouldn't rely on it either. If you decide to take this approach, then I would encourage you to backup the database NOW, and then restore it periodically. Then, let everyone know that they are not supposed to change anytyhing, and if they do, the changes will be lost.
-
George
"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom