Uniqueness of values in specific columns can be enforced in a SQL Server table by creating a unique constraint or a unique index on those columns. In this article, Sergey Gigoyan looks at what the differences between the two are, and how SQL Server handles them both.
Today we have a guest editorial as Steve is away on vacation. You often hear about how important it is to network. This is a story of how my network helped me get a new job.
Learn how to use SSIS to load Delimited Flat Files to staging tables.
A number of new SQL Server PowerShell cmdlets have been released and the Microsoft is asking for feedback on what else you'd like to see.
David Fitzjarrell takes a look at why the mutating table error is thrown, why it's not going to create data problems, and how to possibly fix it.
This article demonstrates how to generate and save an SSRS report to a network folder when an SSIS package is executed.
Knowing what is happening on your systems, and being told when a system is not behaving normally is very important for administrators. Steve Jones has a few thoughts on monitoring today.
It is a good time to get familiar with Azure SQL Data Warehouse. The first objective must be to get data into it. SSIS is a good way to start, and it’s certainly worth gaining confidence with the ETL processes supported by SSIS before setting off in other directions. Rob Sheldon provides a simple guide to getting up and running.
One of the things that can be an issue in database design is the data used to identify a user.
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...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
Hi All I am trying to find 'bad' characters that users might type in....
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