Delivering Rapid Improvements to SSMS
SSMS has spent years being neglected, merely being kept compatible with SQL Server and its features: But now we have, instead, the promise of monthly delivery of new functionality
SSMS has spent years being neglected, merely being kept compatible with SQL Server and its features: But now we have, instead, the promise of monthly delivery of new functionality
Today Steve Jones notes that back doors could be inserted into chips, which would be a huge problem.
With AD Authentication via groups, SQL Server is vulnerable to orphaned Windows users' logins being added to SQL Server at a later date. This article gives an improved user audit script that detects orphaned DB Users and also a delete script.
You work in a shop that puts business or application logic in SQL Server using stored procedures, views and functions to return values to the calling applications or perform tasks. This is not unusual for companies that use the SQL Server layer to perform
Over recent months, Redgate’s development teams have been busy updating the tools in the SQL Toolbelt to support the valuable new functionality released with SQL Server 2016. To achieve this, most tools now support the syntax for SQL Server 2016’s key features, letting you do even more with them. Learn mor.
This Friday, Steve Jones asks if you're like to work remotely. With the trend moving this way, mostly for extra hours, maybe you'd like to move that way for most of your work time.
The Midnight DBAs and Minionware are having a birthday celebration. You can get your present of a free license today only.
For this month's T-SQL Tuesday, Rob Farley takes a look at a couple of unexpected aspects of query plans you might observe when using Temporal Tables in SQL Server 2016.
In SQL 2016 several new security features gets introduced which will help users to protect their data in many ways. New security feature Row Level Security (RLS) which implements the security inside the database itself, not at application level.
Learn how to install and configure your initial DLM Dashboard instance.
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