Are your developers working with live production data, completely made-up synthetic data, or something in between? I posted a poll here on the blog and on a few of my social media feeds, and here were the results:
There are all sorts of coding practices that produce better code. Steve Jones talks about one today.
This tutorial will show how to use an AI model with Python to respond to queries.
Like many relational database systems, MongoDB supports the use of views. A view is a read-only object in a MongoDB
In today's rapidly evolving landscape, managing the security of large and complex database estates is a critical challenge for organizations. Join us for a webinar on Nov 21 covering “Prioritizing security: Essential strategies for IT leaders,” where Redgate’s security experts will share their tips on how you can safeguard your database estate and minimize reputational risk. There will also be a Q&A session where you can get expert advice from our panelists.
As the Simple Talk Editor, I have had the privilege of attending numerous conferences these past few years, and all of them have been somewhere between great and amazing. Still, there is something a bit more special about the PASS Summit. Even before I started this position, I have been to the PASS Summit events […]
If you encounter Django in your environment, are you thinking about SQL Injection and security? If not, read this article and learn how to protect your data.
Steve has a few thoughts on how valuable education can be in your career.
Learn about different ways to improve the performance of full wild card text searches to find strings in SQL Server tables.
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