Risk and Assumptions
Building software always involves risk, but in these tough times, Steve Jones thinks we should be working to lower the risk of IT projects.
Building software always involves risk, but in these tough times, Steve Jones thinks we should be working to lower the risk of IT projects.
SQL Server 2014 introduces enhancements to two common database maintenance operations namely Partition Switching and Online Index Rebuild which greatly increases enterprise application availability by reducing maintenance downtime impact.
Join us for a free day of SQL Server training and networking on September 21 in Providence Rhode Island. Featured speakers include Paresh Motiwala, Wayne Sheffield, and Jason Brimhall.
Dealing with a disaster is a trying experience for anyone, but having to then worry about having the proper software installed can make things much worse. Steve Jones talks a bit about the challenges of worrying about software versions.
In real-world applications, it often makes sense to show denormalized data, such as delimited lists, within the application's user interface. Dwain Camps shows why, and how, the distribution business stores information about 'islands' in sequences in order to track the status of the shipping of a consignment. It makes a great SQL puzzle.
This fall SQLskills is running the SQL track at SQLIntersection, with an amazing lineup of speakers and sessions. Join Paul Randal and Kimberly Tripp in Las Vegas for the event, Oct 28-30.
Join SQL Saturday San Diego for a free day of SQL Server training and networking on September 21st. There will also be a free SQL in the City Session on the 20th presented by Steve Jones and Grant Fritchey.
In part 3 of his thoughts on certifications, Steve Jones gives an idea for how we might move forward from here.
In this Webinar on Tuesday September 12, Louis Davidson will explain the differences between good and bad database design. He'll discuss characteristics such as comprehendible, documented, secure, well performing, and normalized (naturally). Register to come along.
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