db_datareader

External Article

Blocking SQL Server db_datareader, db_datawriter, and db_owner Permissions

  • Article

n a database I currently support, the application makes use of db_datareader and db_datawriter to give permissions to the tables. In a different database, it's even worse as the application uses db_owner. We're adding new tables to both databases and we don't want the application to have access to these tables. How can I deal with the use of these three roles?

2013-04-02

3,632 reads

Blogs

Check your regions people

By

Today I was having a nice discussion with some colleagues about Fabric and pricing/licensing...

Using Git Prune–#SQLNewBlogger

By

As I’ve been working with SQL Saturday and managing changes to events, I’ve accumulated...

Microsoft Purview new data governance features

By

Starting last week is a rollout of the public preview of a new and...

Read the latest Blogs

Forums

Read Only Replica in SQL Server Standard

By Stewart "Arturius" Campbell

Comments posted to this topic are about the item Read Only Replica in SQL...

Identifying Customer Buying Pattern in Power BI - Part 1

By Farooq Aziz

Comments posted to this topic are about the item Identifying Customer Buying Pattern in...

Backup of encrypted databases failing

By Leo.Miller

I've had some backups of my encrypted databases failing with the error "BACKUP 'DBName'...

Visit the forum

Question of the Day

Read Only Replica in SQL Server Standard

Our environment runs using SQL Server Standard. We are implementing Availability groups. Our database has been experiencing high read volumes, so I want to let the application read the Synchronized Secondary replica, as I read that HADR does this. Can we implement this?

See possible answers