Data Lineage: The Next Generation
Bill Lewis describes the benefits of an application development environment in which all data dependencies begin and remain clearly, precisely and explicitly defined.
Bill Lewis describes the benefits of an application development environment in which all data dependencies begin and remain clearly, precisely and explicitly defined.
How quickly should you report a loss of data? It's an interesting question in these security conscious times and Steve Jones talks about
How quickly should you report a loss of data? It's an interesting question in these security conscious times and Steve Jones talks about
How quickly should you report a loss of data? It's an interesting question in these security conscious times and Steve Jones talks about
The OUTPUT clause was a new feature in SQL Server 2005 that can prove very handy in many situations. New author Gennadiy Chornenkyy brings us a look at how you can add this code to your SSIS packages and retrieve ID values back from the database.
New SSD (Solid State Device) hard drives are infiltrating enterprise servers more and more, but are they a good fit for database instances? Steve Jones comments a bit on some news from this past week.
As a telecommuter Steve Jones has found it has increased his productivity, but he's not alone. Sun has examined their own telework program from the energy perspective.
Earlier installments of this series illustrated how to ping the host, how to check all of the windows services related to SQL Server and how to check the hardware and operating system information. Part 4 of this series demonstrates how to get hard disk and network adapter information from the host machine.
SQL Server 2008 offers a wide variety of features and FILESTREAM is one of the most anticipated. This article describes how to configure the FILESTREAM feature.
As IT becomes more and more important to not only businesses but governments, what does that mean in the event of a disaster?
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