Expanding the uses of DBCC CLONEDATABASE
Erin Stellato goes into detail about some practical use cases for a new DBCC command in SQL Server 2014 SP2 : DBCC CLONEDATABASE.
Erin Stellato goes into detail about some practical use cases for a new DBCC command in SQL Server 2014 SP2 : DBCC CLONEDATABASE.
This Friday Steve Jones looks to find out what things help people learn and build skills more readily.
It’s been said that one of the drawbacks to normalization to the third form (3NF) is more cumbersome data extraction due to the greater number of tables. These require careful linking via JOIN clauses. Improper table joining can easily result in erroneous results or even in the dreaded Cartesian Product. In today’s article, Rob Gravelle explores how table joins are achieved in MySQL.
A competition among software bots may foretell a vision of the future for software developers.
Use Powershell to troubleshoot SQL connectivity issues. A way to monitor up-time and connectivity of a SQL server database with some simple Powershell commands.
Rob Farley explains why AT TIME ZONE is his new favourite feature in SQL Server 2016, but also shows that it can make a mess of cardinality estimates.
The SQL Server Error Log is quite large and it's not always easy to view the contents with the Log File Viewer. Greg Robidoux presents an easy way to search and find errors using T-SQL.
This week Steve Jones notes that backups aren't the most important thing for your data. Restores are.
In-memory OLTP was introduced in SQL Server 2014, but greatly improved in SQL Server 2016. If you have a heavily-used transaction-processing that is processing a lot of data, it is definitely worth considering the new 'In-Memory' features of SQL Server 2016. Grant Fritchey explains why.
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