How To Keep Up with SQL Server
It can be a challenge to keep up with the rapidly evolving SQL Server platform. Andy Warren has a few ideas today.
It can be a challenge to keep up with the rapidly evolving SQL Server platform. Andy Warren has a few ideas today.
SQL Saturday #440 is coming to Pittsburgh on October 3, 2015. Now is the time to submit if you'd like to speak at the event.
Building (or rebuilding) a Columnstore index can be a resource intensive operation. In this article, Denzil Ribeiro describes the index rebuild process and index maintenance for clustered Columnstore indexes in SQL 2014.
Detecting file differences on two different web servers using T-SQL.
The latest version of tSQLt is now available with some SQL Prompt snippets to help you get started.
An invitation to hack United's IT systems has resulted in vulnerabilities being found and hackers rewarded for disclosing the issues.
Tim Smith looks at what to take into consideration before building a design to archive old data in SQL Server databases.
Steve Jones discusses the decision to hire someone that fits in with your culture at work, and what that means.
Unlike some other industrial-strength database servers, SQL Server lacks a built-in mechanism for protecting individual data records, called row-level security. This stairway level explores why you might want to use such a low-level granularity of data access security and how you can implement row-level security.
One of the more confusing statistics in Oracle is one called the clustering factor. Associated with an index, it's actually dependent on the table data, more specifically the distance between 'jumps' for a given index key. Commonly, a 'jump' is the number of blocks between rows containing the given index key starting with the first block found containing that key. If that sounds confusing don't despair, David Fitzjarrell explains in detail.
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