Is It Worth Writing Unit Tests?
What's the overhead for writing unit tests? Ed Elliot breaks it down, looking at the ways in which unit tests both take more time and save time.
What's the overhead for writing unit tests? Ed Elliot breaks it down, looking at the ways in which unit tests both take more time and save time.
The job of the DBA is constantly evolving, but one thing has always been critical: access to data.
Database Lifecycle Management (DLM) is about enabling rapid, risk-free database development and deployments. However, the most effective DLM processes actually reach beyond the database. Embracing the full scope of it can be daunting, so Grant Fritchey and Matthew Skelton are making it manageable.
For a large SQL Server database on an Azure VM, backing up the data can have some challenges. In this article, Murshed Zaman focuses on the two most common challenges: size and speed.
BI Architect Bill Pearson continues with the second of a set of articles surrounding a group of MDX functions specialized to support the analysis of data within the context of time / date. In this article, we will explore the OpeningPeriod() and ClosingPeriod() functions, and get hands-on practice with each in meeting sample business requirements.
If you need to receive and process a large volume of of packets of data, such as telemetry, or event-log items, it may be worth considering Azure Event hubs. They aren't like traditional messaging but represent more of a stripped down one-way event processing system for large volumes of data. It could represent a good solution to an ever-present problem, but is it ready for production use? Rob Sheldon investigates.
Handle together SQL Server spatial data features and Reporting Service design tools to build a map-based interactive report.
We must learn to deal with the reality of our situation, along with the limitations.
Inadequate storage is one of the most common bottlenecks seen in subsystem performance. There are a number of reasons for poor storage performance, but measuring it and understanding what needs to be measured and monitored is always a useful exercise.
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