No Limits
There are some very interesting projects being performed with cloud services. Steve Jones talks about a few and the new computing without limits claim from Google.
There are some very interesting projects being performed with cloud services. Steve Jones talks about a few and the new computing without limits claim from Google.
Recently I was supporting a third party application. It queries to determine what tables it has permissions to before it proceeds with the rest of its functionality. We had implemented permissions based on the best practice of creating roles, assigning the permissions to the roles, and then making the users members of the roles. The application was querying INFORMATION_SCHEMA.TABLE_PRIVILEGES and of course didn't find any permissions directly against the user in question. We ended up granting explicit permissions to the user so the application would work, but I'm more interested in the general case. How can I determine permissions for an individual user?
Today Steve Jones talks about the accidental DBA and how they can find themselves in a position where they are responsible, but not well trained. In those cases, it's up to the individual to learn, but also the manager to ensure it gets done.
Sometimes, you can tire of writing the same PowerShell code once again. After this happened to Phil whilst keying in an SMO pipeline to access databases, it occurred to him that he should have only one pipeline to access databases in PowerShell, one reusable pipeline
A free day of SQL training in Iowa City o Aug 11. Come meet other SQL Server professionals in the area.
So you want to group your data for charting in Excel? Here's how, the easy way!
One very handy item Steve Jones found as a DBA was a DBA only database on each instance. Today he asks you if you have one and if not, why not. There are good reasons to have one, and security is usually not a problem.
Continuous integration, or CI, brings developers closer to delivering error-free software flawlessly. Find out how to implement it.
These days it seems there's no shortage of bad managers out there. However the bad ones do more than hurt morale, they actually can impact productivity. Steve Jones wonders why companies don't do more to fix this.
There is a rippling effect from the hack on Yahoo. Those users and passwords are being used on other sites. Steve Jones reminds us that we shouldn't be sharing passwords, and we should educate our users to do the same thing.
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