Steve Jones notes that SQL Injection is still a problem, and while it might be for some time to come, we should not be adding to the issues. Learn how to write secure code.
This PASS VC Webinar will take place August 14, 1PM EDT. Creatively resolving differences and negotiating mutually beneficial agreements is crucial in all walks of life. It’s especially important and challenging in the IT industry where soft skills are not necessarily prevalent. ??In this session, we’ll introduce the basic concepts and precepts that will aid you in negotiating better agreements with your neighbors, peers and co-workers, and even your boss.
K. Brian Kelly is trying to use SQL Server's built-in encryption and sees there are three different options available for an asymmetric key, corresponding to key length. What's the impact of the key length?
Learn how you can build triggers that prevent an update or delete statement from being run without a WHERE clause in this article.
This Friday Steve Jones has a poll asking how you feel about SQL Server for your own projects, or even your company's projects. Is it a given you'd use SQL Server?
A Powershell script that allows you to execute SSIS packages using the traditional Package Deployment Model can be very useful. But what do you do when the execution isn't triggered by the same computer where the target package resides? Marcin Policht offers a solution.
Do you use SQL Doc? We're building the new version, and we'd like your help. Complete the survey for a chance to win a $50 Amazon voucher.
Check Constraints play a very important role in SQL Server as it allows data validation rules to be imposed at the SQL Server instance level itself instead of writing rules for each application.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers