It is no good doing some or most of the aspects of SQL Server security right. You have to get them all right, because any effective penetration of your security is likely to spell disaster. If you fail in any of the ways that Robert Sheldon lists and describes, then you can't assume that your data is secure, and things are likely to go horribly wrong.
2015-05-13
9,527 reads
Sometimes you need to reach outside a database and access data and objects from multiple databases, which raises some security issues and increases the complexity of data access. In this stairway level, you’ll learn about cross-database ownership chaining so that you can reach across database boundaries securely.
2024-05-08 (first published: 2015-04-08)
11,206 reads
2015-03-25
1,768 reads
2015-03-19
1,978 reads
2015-02-10
1,645 reads
2015-02-09
1,616 reads
2015-02-05
1,903 reads
Database ownership is an old topic for SQL Server pro's. Check this simple lab to learn the risks your databases can be exposed to.
2015-01-29
10,875 reads
Alter database owner to SA from any other user details against all user databases
2019-05-03 (first published: 2015-01-13)
1,836 reads
PCI DSS has strict requirements about implementing security updates and using only applications which are supported by the vendors. How do you create a patching policy for SQL Servers?
2015-01-12
5,700 reads
pg_cron is a simple cron-based job scheduler for PostgreSQL that runs inside the database...
By Steve Jones
I heard someone say recently that you can’t change a primary key value in...
By Kevin3NF
Indexes 101: What, Why, and When? “What Is an Index?” I get this question...
Wondering how others keep track of the purpose for SQL Logins? I'm not talking...
Upgrading an instance of SQL Server 2019 to SQL Server 2022 - I am...
SQL Server SSRS 2022. Running into ' SSL Provider, error: 0 - The target...
How can I check what value I used for TEXTSIZE? I ran this code:
SET TEXTSIZE 8096But then deleted the code and couldn't remember. Is there a way to check this? See possible answers