Checking Up on Developers
This Friday Steve Jones has a poll about developers. Help compile a good list of common mistakes made in SQL Server.
This Friday Steve Jones has a poll about developers. Help compile a good list of common mistakes made in SQL Server.
This Friday Steve Jones has a poll about developers. Help compile a good list of common mistakes made in SQL Server.
This Friday Steve Jones has a poll about developers. Help compile a good list of common mistakes made in SQL Server.
Now, Internet-hosted distributed applications with connectivity to internal applications—often referred as Software plus Services (S+S)—are gaining popularity. Organizations are leveraging datacenters hosted by third parties to alleviate concerns about hardware, software, reliability, and scalability. These are just some of the new architecture trends that help you build interoperable applications that scale, reduce capital expenditure, and improve reliability. Cloud computing offers many of these benefits.
To scale your SQL Server properly means to make it bigger and better. But what is the best method for 2008?
I have been a bit lax these past few days, but I have been having a bit of a writers block not knowing what to write about. Well, I realized this evening there is something worth writing about, and it is happening right now on SQLServerCentral.com. An...
Flash. Flash Gordon. There have been a few "Flash"es in Steve Jones career, and the newest one looks interesting.
Script Task in SSIS can provide simpler implementation of complex mail functionality in comparison to Send Mail task.
An auditor has taken a look at our SQL Servers and has told us that we need to audit login failures to the SQL Servers themselves. How do we do this?
If you own a business, I believe that you have a right to make more money than the rest of your employees. You are taking on a risk, and greater risk should result in greater reward, at least that’s how capitalism is supposed to work. But what about management...
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