Downtime
One thing most DBAs try to avoid whenever possible is unexpected downtime. It still happens, and we have to deal with it. This Friday Steve Jones asks in the poll how much it happens to you.
One thing most DBAs try to avoid whenever possible is unexpected downtime. It still happens, and we have to deal with it. This Friday Steve Jones asks in the poll how much it happens to you.
One thing most DBAs try to avoid whenever possible is unexpected downtime. It still happens, and we have to deal with it. This Friday Steve Jones asks in the poll how much it happens to you.
You can read the previous posts here. To finish up my thoughts on networking I want to brain storm some about how we might make it easier and more effective for the average Joe (which is most of us) to network. If you've been to the PASS Summit, or...
This article is the final article in a series that explores new features that are available in SQL Server 2008 Management Studio
The previous installment of "SQL Server 2005 Express Edition" discussed Service Broker's internal activation, which allows you to automate communication between initiator and target. Unfortunately, there are some caveats related to its security context. This article describes their specifics and provides a couple of methods to eliminate any undesirable side effects they introduce.
I diverge a little from the typical coding-based/oriented best practice to one that is focused on governance within public or government organisations with respect to the security of the data in databases used for annual reports. Internal controls fall...
Continuing with his discussion of how to implement a date dimension in SQL Server Analysis services, expert warehousing expert Vincent Rainardi discusses how to use this dimension as a reference dimension as well as other advanced topics.
When reviewing an issue through the Replication Monitor, the error messaging was leaving me wanting more detail to find out why the replication process was failing. So my question is, is there a way to garner more information from the replication agents running via SQL Server Agent?
In which Phil illustrates an old trick using STUFF to intert a number of substrings from a table into a string, and explains why the technique might speed up your code...
This article is part 2 of a 4 part series that explores the internals of SQL Server Integration Services. This article looks at SSIS Transformations and Execution Trees.
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,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
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
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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