This article will help you to schedule jobs in Azure SQL.
Passwords are a problem, especially when we're in a hurry. What should we do?
As announced on June 1, 2016, SQL Server 2016 has reached its general availability. This means that you finally have the option to implement some of its new features in the production environment. While we still have to wait for their full support in Azure SQL Database V12, it is likely that their preview stage will be concluded soon. In this article, we will focus on Temporal tables, which is one example of these new features.
This Friday Steve Jones talks SQL Saturdays and asks how far you've traveled to attend one.
Simon Liew shows how to execute SQL Server DBCC SHRINKFILE without causing index fragmentation and example conditions that cause fragmentation.
Producing a crib sheet for data quality drives a shared understanding of the data used to power the business.
Gathering too much data isn't always helpful, and doesn't necessarily help you make better decisions. However, that's up to you to decide how much is too much.
React is a front-end user interface library developed by Facebook, originally to help them improve their own site. Since then it has grown into somewhat of a phenomenon, with many active users. In this article, Jon Smith provides multiple examples of how to use React with recently released ASP.NET Core MVC, and the existing ASP.NET MVC5 framework.
Today Steve Jones notes that the ability to search if invaluable as the amount of information, or even objects, we deal with grows.
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....
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