PASS Update #4
Last week I posted Update #3 that discussed my first board meeting, but I didn't have time to cover my goals, so I 'll do that and add some other minor items as well.
Last week I posted Update #3 that discussed my first board meeting, but I didn't have time to cover my goals, so I 'll do that and add some other minor items as well.
SQL Server login monitoring and access control are important elements of SQL database security. Learn how DDL triggers can help alert you to security issues.
I should have put this out earlier, before going to the SQL Server Innovators Guild , but I got too busy. Here are my current speaking / teaching engagements for the first half of the year:
A tour of the new Red Gate Software offices from Steve Jones, looking at how a modern software company has set up it's space.
A tour of the new Red Gate Software offices from Steve Jones, looking at how a modern software company has set up it's space.
A tour of the new Red Gate Software offices from Steve Jones, looking at how a modern software company has set up it's space.
Every DBA needs to give serious consideration to the level of antivirus/antispyware protection they need on their SQL Server instances, and to the performance implications of the strategy they choose.
DevWeek is Europe’s leading independent conference for software developers, database professionals and IT architects, and features two dedicated tracks of breakout sessions on SQL Server and related topics, plus optional pre- and post-conference workshops.
Being a DBA demands that you keep up with the latest technology, and conferences are one of the best ways to do that. So, despite the fact that training budgets may be shrinking, I suggest you begin lobbying your manager to attend as many SQL Server events as you can. If you can't get your company to send you to a paid conference, then try to attend one of the free ones, on your own time.
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...
It is Friday, the queries are running, and nobody is watching the bill. That...
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....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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