The Secure Medical Data Challenge
This week Steve looks at the challenges of security for medical data.
This week Steve looks at the challenges of security for medical data.
SQL Server Encryption is an essential part of what is required for protecting data. Column-level encryption can be a very effective way of doing this. In the first in a series of articles on the theme of SQL Server Encryption, Robert Sheldon once more makes it all seem easy.
This is the last week for a discounted registration to SQL Bits 2017. The price goes up after Mar 4, so register today.
Here a quick script showing how to get all the Active Directory users in a AD group.
If your organisation is committed to using Oracle Business Intelligence Enterprise Edition (OBIEE) 10g/11g /12c as their BI solution, you aren't thereby committed to using Oracle throughout your organisation. You can use a range of data sources including SQL Server, and save a great deal of money by doing so. Sadly, Oracle will only support the use of the venerable SQL Server 2008 R2. Zafar Ali demonstrates how to connect OBIEE to the world beyond Oracle.
Today Steve Jones argues the cloud is just another tool for us to use. Not required, not ignored, but considered.
Aaron Bertrand acknowledges that DISTINCT and GROUP BY are usually interchangeable, but shows there are cases where one performs better than the other.
Let's forget the actual PowerShell code for a moment: Why is PowerShell important? Why should I use it? Where did it come from? Why did it take so long to arrive? These and many other basic questions are answered in William Brewer's latest addition to the series that answers those seemingly simple questions that you were too shy to ask in public.
I will describe a simple method anyone can use to obtain lost password information for a SQL Server login.
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