What is SQL Server not good at?
Today Steve Jones talks about some of the problems in SQL Server. Should we be documenting the situations in which features don't work well?
Today Steve Jones talks about some of the problems in SQL Server. Should we be documenting the situations in which features don't work well?
In this series on implementing data services in Azure, Marcin Policht turns his attention to the remediation of incompatibilities resulting from of limitations inherent to Platform as a Service (PaaS) based deployments, which will need to be addressed as part of the migration process.
Steve Jones knows that good development practices require lots of skill and practice, but the basis for stability with your code is version control. He talks about some reasons why you might want to implement it.
For loading text, CSV or XML files into SQL Server, the Log Parser utility, with its amazing SQL engine, is likely to be the obvious choice. Although initially developed purely for converting IIS logs, the Log Parser can turn its hand to a range of formats including even event logs or the Windows registry.
A CLR Procedure that performs multi-threaded fie copies without external command line tools.
How can you measure someone's DBA skills? Steve Jones comments on a new technique that someone suggested to him.
Understanding indexes and how they work can be complicated enough for a Jr. DBA, but throw in all the different options and properties and an index can soon be overwhelming. Brady Upton takes an introductory look at creating an index in SQL Server using SQL Server Management Studio. He explains what each index property is meant for and the various options presented.
Introduction into Locking, Blocking and Deadlocks in SQL Server, and why SQL Server uses these actions.
Like Sherlock Holmes, a DBA needs the sound deductive reasoning to pinpoint the root cause of a crime, in amongst a thousand interesting but irrelevant details.
Today we have a guest editorial from Chris Shaw. After the recent PASS Summit, Chris talks about the value of getting inspired by people he listens to talking about SQL Server.
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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