Loginless In Seattle
Identify orphaned Database Users and differentiate them from "Loginless" Database Users.
2013-05-13
3,140 reads
Security
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,722 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
188 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,025 reads
2013-02-28 (first published: 2013-02-12)
1,146 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
2012-05-25
2,278 reads
The User Defined Server Roles in SQL Server 2012
This article describes how to create user defined server roles and use stored procedures and queries related.
2012-05-25
4,575 reads
Grant Execute to all SQL Server Stored Procedures
With SQL Server 2000 no default server, database or application role was available to be able to execute all stored procedures. With SQL Server 2005, SQL Server 2008 and SQL Server 2008 R2 has this changed with all of the new security features? If not, what options do I have to grant execute rights to the needed database roles?
2012-04-19
2,470 reads
Blogs
Runing tSQLt Tests with Claude
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
Getting Your Data GenAI-Ready: The Next Stage of Data Maturity
By James Serra
I remember a meeting where a client’s CEO leaned in and asked me, “So,...
Learn Better: Pause to Review More
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
Forums
Execute Process Task: Issues encrypting text file using PGP in SSIS 2022
Hello SSC, Has anyone encountered this before??? I have an odd issue that I...
Azure SQL DBA certification
Hello team Can anyone share popular azure SQL DBA certification exam code? and your...
Faster Data Engineering with Python Notebooks: The Fabric Modern Data Platform
Comments posted to this topic are about the item Faster Data Engineering with Python...
Question of the Day
Which Result II
I have this code in SQL Server 2022:
CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
exec('SELECT ProductName FROM product;')
END;
GO
exec etl.GettheProduct
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned? See possible answers