2015-05-21
1,254 reads
2015-05-21
1,254 reads
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,333 reads
2015-03-25
1,774 reads
2015-03-19
1,979 reads
2015-02-10
1,653 reads
2015-02-09
1,616 reads
2015-02-05
1,905 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
11,388 reads
Alter database owner to SA from any other user details against all user databases
2019-05-03 (first published: 2015-01-13)
1,873 reads
By Steve Jones
I had a few random questions from my Running a Local LLM on Your...
By Arun Sirpal
For those entering the AI space whether professionally or personally I wanted to give...
By Steve Jones
Thanks to everyone for attending my session on running a Local LLM. If you...
I have an app that has an address field on the customer and the...
Good Afternoon, I have a Job which "fires" off an SSIS package (that is...
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
How do I easily get the next 12 sequence values from a sequence object?
See possible answers