Software Patents
Patents are one way that governments can spur innovation. However many people think software patents should be eliminated. Steve Jones doesn't think so, but would like reform.
Patents are one way that governments can spur innovation. However many people think software patents should be eliminated. Steve Jones doesn't think so, but would like reform.
When negotiating your salary, it helps to know what the ranges are for your experience and area. Steve Jones gives a little advice today.
Azure SQL Database’s Dynamic Data Masking (DDM) feature limits the exposure of sensitive information to non-privileged users. DDM can mask either the full value or partial value in a column. This method can also mask Social Security and Credit Card Numbers without making any changes to the application. Read on to learn more.
While Name Value Pairs Tables are anathema to Relational Database professionals, it is sometimes useful to consider such a structure in a production application.
This article illustrates the use of User-defined Table Type to improve such handling.
An accident on a ship is being blamed on unclear data visualization.
Some time ago, Phil Factor wrote his booklet 'SQL Code Smells', collecting together a whole range of SQL Coding practices that could be considered to indicate the need for a review of the code. It was published as 119 code smells, even though there were 120 of them at the time. Phil Factor has continued to collect them and the current state of the art is reflected in this article. There are now around 150 of these smells and SQL Code Guard is committed to cover as many as possible of them.
Additional files can be added to to a database to increase the storage. When more data is added to the files, Extended Events shows how SQL Server spreads data across multiple files.
Steve Jones thinks there is a list of core skills that any database developer or DBA needs. This week he asks you for a list of those things you think should be included.
Inside the SQL Server Tacklebox you'll find day-to-day tools and techniques to automate and standardize SQL Server installation, document and report on your servers, migrate data and manage data growth, troubleshoot performance issues, receive notifications of impending issues, secure access to your servers and fight off the data corruption monster.
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