Loginless Database Users and Dynamic SQL
Implement Loginless Database Users to maintain data security and preserve interface when dynamic SQL is being used within a stored procedure.
2013-09-10
7,364 reads
Security
2013-07-12
2,320 reads
Passively detect attempts to guess passwords
Review the error log for possible brute force or dictionary attacks on your SQL Server instance.
2015-05-08 (first published: 2013-05-22)
2,695 reads
Loginless In Seattle
Identify orphaned Database Users and differentiate them from "Loginless" Database Users.
2013-05-13
3,142 reads
Change DB Owner to sa for multiple DB's
Changes DB owner to sa for Online DB's where owner is not sa
2013-04-26 (first published: 2013-04-12)
2,724 reads
Algorithm Secrecy is not Security
This week Steve Jones talks encryption and why you shouldn't be implementing anything you've invented.
2013-03-18
189 reads
Stored Procedures and SQL Injection
Why do stored procedures help with security? In this piece, MVP Brian Kelley explains why SQL Injection and information gathering are hampered with stored procedures.
2015-06-12 (first published: 2013-02-18)
21,027 reads
2013-02-28 (first published: 2013-02-12)
1,147 reads
Protecting the SQL Server Backup folder
I want to backup my SQL Server databases to a folder, but I want to minimize who has access to the folder. In other words, I want to make sure that members of the Windows Local Administrators group don't get to the backups without intentionally trying to bypass the security. How do I do that?
2012-10-02
3,264 reads
Issues Determining an Individual SQL Server User's Permissions
Recently I was supporting a third party application. It queries to determine what tables it has permissions to before it proceeds with the rest of its functionality. We had implemented permissions based on the best practice of creating roles, assigning the permissions to the roles, and then making the users members of the roles. The application was querying INFORMATION_SCHEMA.TABLE_PRIVILEGES and of course didn't find any permissions directly against the user in question. We ended up granting explicit permissions to the user so the application would work, but I'm more interested in the general case. How can I determine permissions for an individual user?
2012-08-02
3,152 reads
Blogs
Rolling Back a Broken Release
By Steve Jones
We had an interesting discussion about deployments in databases and how you go forward...
A bespoke reporting solution doesn’t have to cost the earth
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Forums
Remotely Engineer Fabric Lakehouse objects: The Fabric Modern Data Platform
Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...
Creating JSON III
Comments posted to this topic are about the item Creating JSON III
Testing is Becoming More Important
Comments posted to this topic are about the item Testing is Becoming More Important
Question of the Day
Creating JSON III
In a SQL Server 2025 table, called Beer, I have this data:
BeerIDBeerName 1Becks 2Fat Tire 3Mac n Jacks 4Alaskan Amber 8KirinI run this code:
SELECT JSON_OBJECTAGG(
BeerID: BeerName )
FROM beer;
What are the results? See possible answers