Working Under Pressure
A time of crisis means a lot of things to people in technology, but Steve Jones talks about something that's often forgotten.
A time of crisis means a lot of things to people in technology, but Steve Jones talks about something that's often forgotten.
Not everyone who had to use Management Studio when it first appeared in SQL Server 2005 liked it. The paint was still wet and there was still scaffolding around. To give Microsoft its credit, it has succeeded in transforming it into a much more useful product, in its SQL Server 2008 reincarnation.
Data modeling is based on the precept of knowing your data and knowing how the data is interrelated with other data. Everyone knows their data – right? If so, then why do we have so many problems building systems that do what the users want?
Sun Microsystems built a database application that processes a million messages a second. Steve Jones talks about the achievement.
Sun Microsystems built a database application that processes a million messages a second. Steve Jones talks about the achievement.
Sun Microsystems built a database application that processes a million messages a second. Steve Jones talks about the achievement.
As DBAs we must secure and protect data, but what can we do when there are fundamental issues with the way the systems are designed. Steve Jones comments on problems with voting machines.
Gaining recognition or an award without earning it is something Steve Jones thinks is a problem in society in general, and it's filtered into the IT industry.
DBA's and web developers at our company are experiencing issues with connecting to SQL instances using SQL Server Management Studio and other SQL tools using Windows Integrated Authentication. Our company is large, with well over 70,000 users and groups in Active Directory. When we look in the NT event log on the SQL Server we see both MSSQL and Kerberos errors. What could be causing this?
A series of free, one-day training events are coming in October, 2008 to various locations around the country. See if you can attend one in Olympia, Greenville, or Orlando.
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