SQL Saturday #269 - Exeter, UK
SQL Saturday is coming to Exeter on March 22, 2014. Join Red Gate's David Atkinson and the rest of the speakers at this free day of SQL Server training and networking, organized by SQL South West.
SQL Saturday is coming to Exeter on March 22, 2014. Join Red Gate's David Atkinson and the rest of the speakers at this free day of SQL Server training and networking, organized by SQL South West.
As a break from work, this week Steve Jones wants to know what you wish for. Are there comic book, science fiction, or technological thrillers you'd like to see made into movies?
Come see Grant Fritchey and Steve Jones (from Red Gate Software) and many more SQL Server experts while you enjoy spring in Orlando, FL at SQL Intersection.
There are a number of real-life reporting tasks in SQL that require a 'gaps and islands' analysis. There are a number of techniques around that work, but finding ones that scale well makes for a tougher, but interesting, challenge.
Steve Jones has a problem with the inconsistency of the CREATE TABLE statement in SQL Server and has an idea on what to do.
This article will help us identify the backup which was used to restore the database. This may seem simple when the database backup is from the same server but the complications begin when the backup is not from the same server.
In this tip, Sadequl Hussain will try to list a few areas DBAs need to cover when they are designing new systems or reviewing proposed solutions.
A SQL Server database can easily be seen as a bottleneck as all data must be retrieved from a single machine. However a caching strategy in your application and alleviate load and improve performance.
Views are a valuable tool for the SQL Server Developer, because they hide complexity and allow for a readable style of SQL expression. They aren't there for reasons of performance, and so indexed views are designed to remedy this shortcoming. They're great in certain circumstances but they represent a trade-off, and they come with considerable 'small print'. Jes Borland explains.
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
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,...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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