Go Small
The SQL Server community is amazing, and Steve Jones hopes we continue to be close as we grow. He brings light on an idea to grow us larger, but smaller.
The SQL Server community is amazing, and Steve Jones hopes we continue to be close as we grow. He brings light on an idea to grow us larger, but smaller.
Voting is now open for the Tribal Awards. Vote for one of the 5 finalists in each category to win a fabulous* prize.
This article will discuss a case study of utilizing a SSIS package to export a table that has columns with data type varchar(mx) and text to an Excel file.
Kathi Kellenberger demonstrates how to start adding visual flair to your SSRS reports, using its impressive set of visual controls, ranging from basic charts to gauges, indicators, sparklines, and maps.
When undisciplined users access your search forms, you can control their behavior and limit the results they're presented with in various ways.
Steve Jones notes that disasters come in all shapes and sizes, but a little prep that you might not have thought of can reduce the scale of the issues.
Considering that SQL Server 2014 Natively Compiled Stored Procedures are compiled into binary code, you may have asked yourself if it's possible to monitor statement execution. In this tip Daniel Farina explains how you can monitor SQL Server Natively Compiled Stored Procedures.
Steve Jones contemplates employment and the future of the last job he'll have. This Friday he asks you if this might be yours.
In my previous article we discussed Change Tracking which is one of the new technologies introduced by Microsoft. This article will focus on Change Data Capture.
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...
It is Friday, the queries are running, and nobody is watching the bill. That...
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....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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