Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
hamipers
Starting Member
5 Posts |
 Posted - 2005-11-21 : 02:14:19
|
| Hi everybodyI have an ASP.NET project based on a SQL Server 2000 database. I have uploaded both of them in a remote host. My friend has the access to the host. I'm worried if he can download the MDF database file and manipulate the rows and upload it again. I wonder what i can do in such situations where some ppl have a shared access to a same database. Simply he could download the database and open it in Enterprise manager and manipulate data. How can i restrict access to a SQL Server 2000 database so that they cant open and edit data? Something like 'WTIH ENCRYPT' in stored procedures that makes the local user have no access to the stored procedure text. I thought of writing a trigger which can prevent deletion. But my pessimistic mind told me he can remove the trigger simply n still be able to delete rows. Please help me out.Thank u so much in advance |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2005-11-21 : 05:48:56
|
| Don't give access to the folder with the database files.He wouldn't be able to upload the .mdf if the server is running - and would have to copy the tr log file as well.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Access Privillege