The One True Script
Phil Factor less-than-fond memories of the days of the One True Source Script. However, despite recent advances, he wonders just how much smoother team-based database development really is.
Phil Factor less-than-fond memories of the days of the One True Source Script. However, despite recent advances, he wonders just how much smoother team-based database development really is.
This challenge involves converting numeric values from binary format to hexadecimal format.
Today we have a guest editorial from Wendy Pastick, co chair of the Women in Technology Virtual Chapter. Today Wendy takls about how men and women handle their careers.
Geography is one of the spatial data types introduced in SQL Server 2008. One of the characteristic of the geography data type is that it can accommodate any supported geometry based on any supported spatial reference system in the same field. So if the data that is stored in a column of geography data type is not standardized, it can be a very tedious and resource intensive task to figure out the geometry and spatial reference system associated with each value. To deal with this issue, we need to standardize the data stored in a field of that has the geography data type and in this tip we will look at how to deal with this issue.
Many IT Pros can relate to the the Lone Ranger. With the aid of but one trusty side kick, the...
This article discusses about 'Partitioning'. In this detailed article, a particular emphasis is placed on the implementation of Partitioning in SQL Server.
It was a year ago that Microsoft shipped PowerShell 2. Jonathan Medd lists the top ten reasons why PowerShell 2 should be an important tool for your work
I spent this past weekend traveling to and attending SQL Saturday Colorado in the outskirts of Denver. This was the...
This past weekend was the first SQL Saturday in Colorado, and it went very well. I think everyone enjoyed it,...
There's a SQL Server quiz taking place during the next 31 days, challenging you to answer questions from a number of SQL Server experts and MVPs.
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 Extreme DAX: Take your Power...
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
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