Put your Database under Source Control
This article will walk you through a demostration on linking your DB to SubVersion with RedGate SQL Source Control.
2017-01-18
4,708 reads
This article will walk you through a demostration on linking your DB to SubVersion with RedGate SQL Source Control.
2017-01-18
4,708 reads
Aaron Bertrand takes an initial look at the performance of a new function, STRING_AGG, in SQL Server v.Next CTP 1.1.
2017-01-18
3,620 reads
When deploying SQL Server in an Azure virtual machine, you can take advantage of several Azure Infrastructure-as-a-Service (IaaS) features that enhance performance of the SQL Server database engine. This article explores a couple of these enhancements, with a particular focus on increased I/O throughput facilitated by the Solid State Drive (SSD) storage available on most Azure virtual machines (VMs).
2017-01-17
5,354 reads
Understand how to use the SQL UNPIVOT statement and then an equivalent using XML and XPath Querying in SQL Server.
2017-01-16
5,032 reads
Learn how to extend DevOps practices to SQL Server databases in our free demo webinar on January 17th. Microsoft Data Platform MVP, Steve Jones will demonstrate how Redgate’s database automation tools plug into Git, Jenkins & Octopus Deploy. Learn how to branch and merge with SQL Source Control then automate the build and deployment of changes with DLM Automation. Register now.
2017-01-16 (first published: 2017-01-11)
5,646 reads
You can easily use PowerBI Desktop to show graphically how your database is growing, which tables are taking the most space, how various parts of SQL Server is consuming memory, its use of indexes and so on. Sure, you can create graphs in SSMS, but with PowerBI, you can create reports that you can then publish to others, and which allow drill-down. It is a great way to get familiar with PowerBI Desktop as well. Rob Sheldon shows how simple it is to do.
2017-01-16
3,767 reads
Managing personally identifiable information when moving databases to unsecure environment can be challenging. With this flexible and extendable solution for scrubbing it, you can save yourself some time and effort.
2017-01-13 (first published: 2015-01-06)
15,973 reads
A “multi-subnet” environment is defined when the OS cluster used as the backbone for AlwaysOn has server nodes that are located in multiple/different subnets. Deploying SQL Server AlwaysOn Availability Groups requires a Windows Server Failover Clustering (WSFC) cluster and each availability replica of a given availability group must reside on a different node of the same WSFC cluster. This post from Manvendra Singh will help you in configuring an HA and DR solution for SQL Server AlwaysOn in multi-subnet networks.
2017-01-13
3,309 reads
Learn how easy the new SQLServer module makes backups of SQL Server databases.
2017-01-12
35,831 reads
Finding the nightly job failures is just one of a DBA's morning rituals. It is fairly easy to scan all the email with a number of creative search criteria, but what if you would like a more automated approach? Read on to learn how to find and report all job failures using a script.
2017-01-12
4,563 reads
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...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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