Adding Cookie Consent to SQL Server Central
We are adding a consent form to the SQL Server Central website to allow our cookies.
We are adding a consent form to the SQL Server Central website to allow our cookies.
Learn about the benefits of mixed extent allocation in SQL Server 2016, along with how you can check this setting or enable it in your database.
An update from 37 Signals/Basecamp shows their expatriation from the cloud has been a success. Worth reading before you make too many moves to the cloud.
But nowadays, most services are in the cloud. They're not on your servers; they're somewhere else. With most software-as-a-service (SAAS) offerings, you don't have many options to configure connectivity. What if you need data from one SaaS service into another?
Azure Data Studio (ADS) is a cross platform query tool for SQL Server. Learn how to get started using ADS to work with your SQL Server instances.
In this article, we will examine how to use Azure Data Studio with a git repository for storing code.
This guide helps you get started on troubleshooting some of the common issues in AlwaysOn Availability Groups and monitoring AlwaysOn Availability Groups. It is intended to provide original content as well as a landing page of useful information that is already published elsewhere.
The use of statistics in SQL Server is tightly embedded in the query optimizer and query processor. The creation and maintenance of statistics is usually handled by the SQL Server engine, though many DBAs and developers know that periodically we might need to update those statistics to ensure good performance of queries. SQL Server 2019 gives us more options.
This Data Saturday Event is being jointly developed by the Albuquerque Data Platform Users Group, Arizona Data Platform Users Group, and the Santa Fe Data Platform Users Groups. This event will include sessions on many Microsoft Data Platform related topics. Join us on May 15, 2021.
Learn about best practices for developing SSIS packages that you want to execute from SQL Server Agent and the steps to follow.
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