2018-02-05
778 reads
JSON
2018-01-29
941 reads
Importing JSON Data from Web Services and Applications into SQL Server
To support many applications, it makes sense for the database to work with JSON data, because it is the built-in way for a JavaScript or TypeScript application to represent object data. It can mean less network traffic, looser coupling, and less need for the application developer to require full access to the base tables of the database. However, it means that the database must do plenty of checks first before importing. Phil Factor explains how it can be easily done.
2017-12-04
4,513 reads
Consuming hierarchical JSON documents in SQL Server using OpenJSON
Over the years, Phil was struck by the problems of reading and writing JSON documents with SQL Server, and wrote several articles on ways of overcoming these problems. Now that SQL Server 2016 onwards has good JSON support, he thought that the articles would be forgotten. Not so, they continue to be popular, so he felt obliged to write about how you can use SQL Server's JSON support to speed the process up.
2017-11-15
3,562 reads
Representing a simple hierarchical list in SQL Server with JSON, YAML, XML and HTML
How difficult can it be to produce a simple hierarchical list in JSON, YAML, XML and HTML from a SQL Server table that represents a simple hierarchy within an organisation. Well once you know, it is easy and William Brewer is on a mission to tell you how.
2017-09-28
6,087 reads
2017-06-15
1,011 reads
SQL Server 2016: built-in JSON Use case scenarios
There's built-in JSON support starting with SQL Server 2016. Does that mean we should all ditch XML and start using JSON? It depends mostly on the target of your data output processing.
2016-08-16
5,298 reads
2016-07-05
1,041 reads
2016-06-24
1,407 reads
2016-06-13
1,231 reads
Blogs
Five Ways Redshift Serverless Quietly Eats Your Budget
It is Friday, the queries are running, and nobody is watching the bill. That...
A Career of Memories
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Forums
What is the Cloud?
Comments posted to this topic are about the item What is the Cloud?
Changing the Schema
Comments posted to this topic are about the item Changing the Schema
Index Fragmentation Explained: Page Splits, Logical Reads, and What to Do
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
Question of the Day
Changing the Schema
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