Azure SQL Database Business Continuity Enhancements
Marcin Policht provides an overview of a number of new features that facilitate Azure SQL Database business continuity.
2018-08-28
2,456 reads
Marcin Policht provides an overview of a number of new features that facilitate Azure SQL Database business continuity.
2018-08-28
2,456 reads
NoSQL databases like MongoDB are gaining popularity, but using the right tools for the job at hand is most important. In this article, Phil Factor demonstrates how to work with a MongoDB database and how to use PowerShell with MongoDB so that the process can be automated.
2018-08-27
3,230 reads
Erik points out a few things that SQL Server should offer to configure by default.
2018-08-24
4,779 reads
Creating resources in Azure, while not difficult, can be time consuming if you use the manual steps. One way to automate the process is by using JSON templates to save time and enforce standards. In this article, Brian Flynn describes how to create JSON templates for deploying a network with virtual machines.
2018-08-23
3,050 reads
In SQL Server 2005 by default users of a database that are only in the public role cannot see the definitions of an object while using sp_help, sp_helptext or the object_definition function.
2018-08-22
3,287 reads
When you are setting up a new SQL Server machine you need to determine how big you should make tempdb. To make sure you size tempdb appropriately you should monitor the tempdb space usage. If there are autogrowth events occurring after you have recycled SQL Server than you might want to increase the size of your tempdb data files. If tempdb never uses most of the tempdb space, then you might want to consider decreasing the size of tempdb.
2018-08-21
4,154 reads
In this article of the Power BI series, Robert Sheldon demonstrates how to work with the Power Query M language to import and transform data.
2018-08-20
2,844 reads
Before you go live, test your backup and CHECKDB speeds.
2018-08-17
4,748 reads
Along with the GDPR, regulations require that confidential data is protected and used properly. In this article, William Brewer discusses the ways that data manages to migrate around the organisation and the challenges found in protecting that data.
2018-08-16
3,193 reads
In this webcast, Tim Smith takes a look at various tips and tricks to assist you with performance tuning your SQL Server databases. Knowing how to find and resolve problems is key to improving performance, so join him to learn how to optimize your systems
2018-08-15
4,840 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