Upgrade and Refresh, or Not?
Today we have a guest editorial from Andy Warren that looks at the upgrade cycle and how that affects our jobs.
Today we have a guest editorial from Andy Warren that looks at the upgrade cycle and how that affects our jobs.
After finding it difficult to find seriously useful information on Azure blob storage written after Storage Client Library 1.7 (and we’re on 4.something now), Robin Shahan decided to try and fill that gap with this article.
In the chapter 18-22 we explained how to work with Microsoft Excel to Access to the Data Mining information. This time, we will explain how to work with Microsoft Visio.
In the chapter 18-22 we explained how to work with Microsoft Excel to Access to the Data Mining information. This time, we will explain how to work with Microsoft Visio.
A guest editorial from Tim Mitchell today looks at keeping track of what we have done in our careers, and the value that it gives us.
There are different techniques to optimize the performance of SQL Server queries but wouldn’t it be great if we had some recommendations before we started planning or optimizing queries so that we didn’t have to start from the scratch every time? This is where you can use the Database Engine Tuning Advisor utility to get recommendations based on your workload.
One of the main purposes of placing a database under source control, alongside the application code, is to allow team collaboration during development projects. The Version Control System (VCS) stores and manages all of the project files, maintaining an audit trail of what changed, and who made the change. Each team member can work on a file, or set of files, and submit their changes to the VCS to make them available to other team members. They can also inspect the VCS to discover recent changes made by other team members.
Tony Davis answers 10 surprisingly tricky questions about SQL Server Transaction Log.
How do you make data available to analysts who want to blend data with R or Power Query tools? Why with OData services.
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