Mining for Quitters
Google is trying to figure out who might quit the company, using their own custom application. Steve Jones thinks this is a great idea and wishes more companies would do it.
Google is trying to figure out who might quit the company, using their own custom application. Steve Jones thinks this is a great idea and wishes more companies would do it.
This week Steve Jones looks at a few tools that can help your productivity and links to a few more.
There are a few challenges associated with deployments of data services in Windows Azure, focusing in particular on SQL Database. In this article we turn our attention to an actual deployment and migration of locally stored data to SQL Database.
This article uses XML to deal with optional parameters along with multiple parameter passed into a stored procedure. (Note: We are re-running this as we had a newsletter issue last week)
It's the last Friday of 2013 and Steve Jones asks you to look back at the year. What stands out in your mind that relates to SQL Server.
You may think that if your database has backed up without errors, that it's going to restore without errors. Think again, says Paul Randal.
Every DBA needs to know about SQLPSX, the PowerShell module library that is built by DBAs for DBAs, and designed to provide intuitive functions around the SMO objects. Laerte Junior, who is one of the developers on the open-source project, describes how to use it.
Steve Jones doesn't think that it matters which platform you choose. It's more about the people you have.
Although BIML is very powerful, you wouldn’t use it to generate one package at a time. Using metadata, we can generate multiple packages on the fly. Koen Verbeeck illustrates how to convert the BIML script for generating the import package to a dynamic package generating machine.
How to Compare Rows within Partitioned Sets to Find Overlapping, Contiguous, or Gap dates
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