A Release from Data
What do you do when work is too frustrating. Steve Jones talks about finding a way to release stress and frustration.
What do you do when work is too frustrating. Steve Jones talks about finding a way to release stress and frustration.
What do you do when work is too frustrating. Steve Jones talks about finding a way to release stress and frustration.
This article describes the use of BI in Collaborative Planning, Forecasting and Replenishment
Far too often, people who are not trained database administrators somehow end up responsible for a database. They lack the proper training and knowledge to maintain their database, and problems begin to develop. Here’s a primer for all those involuntary DBAs who need a crash course in database maintenance best practices.
Learn how you can add a new database to your instance if you receive the MDF and LDF files from another source. MVP Brian Knight covers this very useful technique that is used for moving databases to new instances, servers, or even recovering from an disaster.
SQL Server trainer and expert DBA, Andy Warren, thinks that everyone should have a philosophy about security. He starts this installment in looking about how to assign administrative privileges.
Do you avoid certain SQL functionality because you have been told you should NEVER use it?
This paper presents an approach to the definition of function points within database-centric business information systems, the process of counting function points, .
Statistics update date is stored as metadata on the SQL instance, but after a great deal of research against the system tables and DMVs I realized that this information is not readily exposed to the DBA via any other method than the STATS_DATE() function or the SQL Server Management Studio graphical user interface (GUI).
System administrators have a lot of power and temptation to use it. Steve Jones talks about the need to resist temptation and the need for oversight.
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