Database Nonsense - Unstructured Data
Sloppy terminology leads to big misunderstandings. Terms don't get much sloppier than "Unstructured data".
Sloppy terminology leads to big misunderstandings. Terms don't get much sloppier than "Unstructured data".
Learn how to generate Registered Servers with PowerShell in this article.
Master Data Services (MDS) is Microsoft's platform for supporting Master Data Management (MDM). A system like MDS, if properly maintained, gives organisations a powerful alternative to increasingly having to centralize databases as a way of preventing data from getting out sync or become inconsistent, and a reliable way of managing the flow of data through corporate IT systems. It makes microservice architectures realistic. Hari Yadav shows you how to get up and running with MDS.
EzAdo is a very simple api built to exploit some new features of SQL 2016. It combines software, convention, and creativity to get more done in less time.
If you are holding, in your organisation, personal data about real people or commerce, it is wrong, and in many cases illegal to do database development work or testing using your production data. This, of course, probably applies to a minority of database systems, but data breaches caused by attacking backups or copies of production […]
Paul White shows that SQL Server sometimes produces very misleading information about the impact of sort operations.
Introducing JSON Select - a new library that makes it easy to pull values out of JSON strings in SQL Server 2005+
Glenn Berry discusses the ever-changing landscape of memory/storage technology, and how it relates to SQL Server workloads on Windows servers.
In this post I will attempt to explore simple commands to manipulate data pulled in from a SQL database into R.
Executing R scripts can be a heavy load. Today Steve Jones wonders if SQL Server is the best place to execute these.
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