Daniel Calbimonte shows how the Feature pack in SQL Server Integration Services can connect to Azure to automatically copy your SQL Server database backups.
2016-10-18
4,153 reads
Take a look behind the scenes to learn more about Redgate’s development challenges, what role the SQL Toolbelt plays, and which releases are coming up.
2016-10-18
2,708 reads
See how the OVER() clause was used in a live system to fix overlapping field version numbers.
2016-10-17
2,406 reads
A free day of training on Monday, October 24 in Seattle this year. Join MCMs, MVPs, and Friends of Redgate for a free day of training.
2016-10-17 (first published: 2016-09-21)
6,162 reads
SQL Server's In-memory OLTP is fast, due to its multi-valued concurrency control (MVCC). MVCC avoids the need for locks by arranging for each user connected to the database to see a snapshot of the rows of the tables at a point in time, No changes made by the user will be seen by other users of the database until the changes have been completed and committed. It is conceptually simple but does the user always see the correct version of a row under all circumstances? Shel Burkow explains.
2016-10-17
3,150 reads
You should stick to using tables in SQL Server, rather than heaps that have no clustered index, unless you have well-considered reasons to choose heaps. However, there are uses for heaps in special circumstances, and it is useful to know what these uses are, and when you should avoid heaps. Uwe Ricken explains, and demonstrates why you'd be unwise to use heaps rather than tables when the data is liable to change.
2016-10-14
3,646 reads
It’s often useful to be able to create a directory of object-level scripts from an existing database, for example to put a database into version control, or search through a directory of scripts. In this simple ‘how to’ article, Feodor Georgiev expands on the four most common reasons, and shows how simple it is using SQL Compare.
2016-10-14
3,220 reads
SQL Server 2016 introduced three new objects to deal with the greater demand of data; John Miner takes a look at this new functionality.
2016-10-13
4,605 reads
2016-10-12
109 reads
Rangarajan Srirangam from the Azure Customer Advisory Team shares some tips and techniques to help achieve an efficient data migration to Azure SQL Data Warehouse.
2016-10-12
2,674 reads
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