The Database Weekly Update for July 7, 2008
Intel is moving in the direction of more and more cores on a single CPU, so what does that mean for programmers?
Intel is moving in the direction of more and more cores on a single CPU, so what does that mean for programmers?
Intel is moving in the direction of more and more cores on a single CPU, so what does that mean for programmers?
Intel is moving in the direction of more and more cores on a single CPU, so what does that mean for programmers?
Many times people come across the Coalesce function and think that it is just a more powerful form of ISNULL. In actuality, I have found it to be one of the most useful functions with the least documentation. In this tip, I will show you the basic use of Coalesce and also some features you probably never new existed.
Two longtime members of the SQLServerCentral.com community received the well-deserved MVP status this week. Congratulate Jeff Moden and Michael Coles.
The problem arises when the hierarchy level increases as SQL Server is limited to 32 levels of recursion. We need a better way to implement recursive queries in SQL Server 2005. How do we do it?
This article is Part 2 in the series which explores the options available in SQL Server 2005 for Slowly Changing Dimensions
Do you deal with data or information? Do you know the difference and are you transforming one into the other. Steve Jones comments on the state of many companies' data.
Continuing on with his series on building a game in SQL Server, Steve Fibich talks about some more of the tables and the data they contain.
When a team is developing a database application, it is a mistake to believe that deployment is a simple task. It isn’t. It has to be planned, and scripted. Alexander Karmanov describes many of the problems you’re likely to meet, and provides an example solution that aims to save the DBA from the nightmare complexity of an unplanned deployment.
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