SQL Server DBA On-Boarding Checklist
How can we be sure that the new DBAs are productive a soon as possible? How can we use highly qualified contractors in the most effective way from day one?
How can we be sure that the new DBAs are productive a soon as possible? How can we use highly qualified contractors in the most effective way from day one?
The Execute Package Task and a second instance of Business Intelligence Development Studio can be a satisfactory method of background execution of SSIS packages in batch mode when you don't have access to Integration Services.
Team building isn't easy, but important for people to work together well.
To achieve gains from Database Lifecycle Management in general, and in Continuous Deployment in particular, it pays to aim for lightweight but consistent techniques and processes, refining them iteratively in the light of experience. Edward Elliott describes a Test-driven development process for developing SQL Server databases that worked for CD, based on a series of steps. Though the tools for CD may be necessary, they are not sufficient, without an effective structured process.
One of the key tenets in DevOps is to involve the Operations team in the full software development lifecycle and, in particular, to ensure that operational requirements are incorporated...
In this article, we will show how to create a WPF application and show how to insert data to ASDW.
What makes SQL Server professionals stick together? Can we draw any conclusions from this?
Practice makes perfect. That’s true of everything, including disaster recovery. If you aren’t already testing your DR plan, you should be - here’s what you need to know to get started.
The majority of Azure SQL Database related features reach their General Availability (GA) stage relatively quickly. There are however, some exceptions. The most prominent example in this category is likely Azure SQL Data Sync, which has remained in Preview since its introduction 7 years ago. Fortunately, there are signs that this service might be finally reaching production-ready state. In this article, Martin Pollicht introduces its main characteristics.
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