0

I am a Junior DBA trying to figure out how to add specific security to specific accounts.

So we have a database that allows analysts to create their own tables/views and mess around with data in with no repercussions to the existing important databases. Each user will make their own views/tables called User1.Address for example. And user2 can make a view/table with the same name but as User2.Address.

How can I make it so that User1 can view a table that User2 makes but cannot alter or delete their created tables/views?

3
  • what do you mean by saying "can view a table that User2 makes", do you mean SELECT o just VIEW DEFINITION? Commented Mar 6, 2024 at 14:57
  • So they can do a basic SELECT statement, and even see it in the list of tables and views. But cannot make any changes, i.e.ALTER, DELETE, UPDATE etc, to the table. Commented Mar 6, 2024 at 16:06
  • Do you have users where someone creates their schema o do you use Windows Groups as users so it is SQL Server that creates schemas that correspond to user Windows account? Commented Mar 6, 2024 at 17:17

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.