DBAs and the art of persuasion
How does a DBA go about "pitching" for money for a software tool, or any other resource? And what factors affect the likelihood of success? We all think we know, but could we do this part of the job more effectively?
How does a DBA go about "pitching" for money for a software tool, or any other resource? And what factors affect the likelihood of success? We all think we know, but could we do this part of the job more effectively?
Would you want to have your pay docked for time spent rebooting? It seems some companies are trying to do just that.
Learn how you can monitor the SQL Server instances for failover of a cluster or a restart.
You likely will need to test data against SQL Server 2008 and SQL Server 2005, but ordinary backups are incompatible. Use SQL Server 2008's Generate SQL Server Scripts Wizard to push your SQL Server 2008 data back into SQL Server 2005.
With the start of a new year, Steve Jones gets back to the car updates with a look at winter driving and changes in the car industry.
With the start of a new year, Steve Jones gets back to the car updates with a look at winter driving and changes in the car industry.
With the start of a new year, Steve Jones gets back to the car updates with a look at winter driving and changes in the car industry.
Access can offer a lot of help with missing values, but finding and generating missing values in a field of sequential values requires a bit of code. Find it here.
Continuing the conversation I began in Part 1 & Part 2, today I want to ruminate some more on networking. I've had a good discussions about networking since I wrote the first two parts, with a focus on the value of networking.
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 SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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