Data Masking: Static vs Dynamic
Learn about how static data masking differs from dynamic masking and learn which one might be best for your organization.
2022-10-07
3,159 reads
maxtardiveau
Linked Servers: a Peek Behind the Curtain
Learn how a linked server caused an issue with Gallium Data.
2022-07-15
5,024 reads
Can We Please Stop Sending Passwords Over the Wire?
While analyzing SQL Server's network protocol, I came across a weird fact: when a database client logs in using SQL Server authentication (as opposed to Windows authentication), it has to send the user's password to the server, in blatant violation of common security guidelines. At first, I couldn't believe it; SQL Server generally does an […]
2022-03-02
5,144 reads
Query control made easy
Overview As we all know, data security is a never-ending battle. Every day, we hear of new data breaches. It's a hard problem, and there is no single solution, other than a defense in depth. Let's look at one of those defenses for databases: query control. Query control is a simple idea: most applications access […]
2022-01-07
3,854 reads
SQL Server Data Classification Comes Alive
Overview Microsoft SQL Server 2012 introduced a feature called data classification, which allows you to mark certain columns with labels, indicating that these columns contain sensitive or special-handling data. For instance, you may want to mark a column containing credit card numbers as "confidential", or sales numbers as "management only". The problem is that you […]
2021-12-10
4,888 reads
SQL Server Data Masking: a comparison with Gallium Data
Introduction In SQL Server 2016, Microsoft introduced a new feature called dynamic data masking, which allows you to mask the values of certain columns and keep that data hidden from certain users, without having to modify your applications. Let's take a look at how SQL Server does data masking, and compare it to the way Gallium Data […]
2021-12-03
1,693 reads
SQL Server Row-Level Security: A Comparison with Gallium Data
A quick look at how the native SQL Server Row-Level Security compares with Gallium Data's solution for limiting access to rows of data.
2021-11-15
2,904 reads
Blogs
Degrees and Trade Schools
By Kevin3NF
Can we normalize a couple of things? 1 – Trade Schools. Back in the...
Unlock the Power of Your Data: From Basic to Advanced Data Analysis
Data isn't just about numbers and spreadsheets. It holds stories, patterns, and the answers...
Attacking the Weakest Link
By Brian Kelley
When I look at a system and think about its security model, the first...
Forums
Inserting 100K rows Performance - Baseline Performance
We're trying to understand how quick new versions of SQL server can be. Obviously...
plugging a repo version number into the tabular model
hi we run 2019 std. we saw this week that someone hid 3 important...
The "ORDER BY" clause behavior
Comments posted to this topic are about the item The "ORDER BY" clause behavior
Question of the Day
The "ORDER BY" clause behavior
Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:
create table t1 (id int primary key, city varchar(50)); insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);If we execute the following query, how will the records be sorted in both environments?
select city from t1 order by city;See possible answers