DBAs and the ITIL Framework, Part II: Asset Management
See how the ITIL Framework's Asset Management standards make the DBA's job easier. Use the CMDB and DML to keep your data assets under tight control.
See how the ITIL Framework's Asset Management standards make the DBA's job easier. Use the CMDB and DML to keep your data assets under tight control.
This week Steve is asking what jobs you might choose if you had the chance, as well as those you enjoyed, or perhaps dreaded.
Jon Hayman explains the Azure-tailored metrics and alerts in SQL Monitor that track use of the limited compute resources available to an Azure SQL Elastic Pool, and to each of the databases in it.
I don’t have a problem with triggers. They get the job done when you need to implement business logic in a hurry, and you’re not allowed to change the application. As long as you keep the number of statements to a minimum (say, 2-3), and don’t try to do something really slow like fire up a cursor, triggers can be an efficient way to solve hard problems quickly. However, most triggers I run across have a really, really dangerous bug.
This is the wrap up of this series on a system for developers to restore production database in test. It gets pretty detailed on the web setup side.
Cosmos DB is Microsoft’s highly scalable, NoSQL database platform running in Azure. It supports four API models, including Key-Value pair and Documents. Pushpa Sekhara provides an overview of Cosmos DB, including some best practices to improve performance.
Today we have a guest editorial from Andy Warren, looking at learning.
In this series of tips we will look at different ways using temporary data in SQL Server along with examples. In this first part we will cover some reasons for doing this and different types of temporary data stores.
Steve Jones talks about careers, and where you might take your career over time.
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