2020-04-21
476 reads
Encryption
2020-04-07
211 reads
Secure Enclave Concerns
A new security flaw in Intel SGX is found by researchers. This may or may not be a problem, but you should be aware.
2020-03-14
128 reads
2020-01-07
687 reads
SQL Server Transparent Data Encryption vs. NetLib Encryptionizer
Between the legislation over the years (HIPAA, GLBA, GDPR, CCPA, etc.) and data breaches from large organizations that seem to pop-up in the news on a monthly basis, SQL Server database encryption is critical for our industry. SQL Server ships with a few options for a native encryption implementation (Column Level Encryption, Transparent Data Encryption, Data Masking, Always Encrypted), that all provide value in particular situations, but none of the options all seem to address all of the needs. What is the best way to encrypt our SQL Server data?
2019-12-26
Moving Encrypted Data to Azure SQL Database
Learn how you can move encrypted data from on premises SQL Server to Azure SQL Database.
2019-11-26
2,521 reads
6 steps to a more secure SQL database
Security is often something people think about only after they have had a problem. Given that the average cost of a data breach is $3.92 million (SecurityIntelligence 2019) and ransomware attacks have increased 97% over the past 2 years (PhishMe 2019), the "if it's not broke, don't fix it" approach can clearly be catastrophic. Here […]
2019-10-07
9,386 reads
Transparent Data Encryption and Extensible Key Management – Better Together
Learn how you can secure your TDE environment by separating your key from the server using Extensible Key Management.
2019-09-30
9,465 reads
SQL Server 2016 - Always Encrypted
Always Encrypted is a new security feature which was introduced in SQL Server 2016. Always Encrypted is a technology to ensure the data stored in a database remains encrypted at all times during SQL Server query processing. Always Encrypted allows clients to encrypt sensitive data, such as credit card numbers and national identification numbers, inside the […]
2021-05-21 (first published: 2019-09-05)
14,005 reads
2019-07-02
781 reads
Blogs
When Your Microsoft Fabric Capacity Runs Out: Optimize, Scale Up, Scale Out, or Isolate?
By James Serra
Microsoft Fabric makes it wonderfully easy to put many analytics workloads on one platform....
Accessing the Data API Builder MCP Server from VS Code
By Steve Jones
I recently started playing with the MCP Server for SQL Server, which is a...
From DBA or Data Engineer to AI Engineer: A Realistic Path
If you spend your days tuning queries, managing pipelines, or keeping a production database...
Forums
STRING_AGG DISTINCT
Has anyone written a wrapper function (or similar) around STRING_AGG() to allow the retrieval...
In-place OS upgrade or migration to new OS?
Putting this here as we're currently on SQL Server 2019 installed on Windows Server...
Never is Not the Policy
Comments posted to this topic are about the item Never is Not the Policy
Question of the Day
Rebuilding All Indexes
I have added a few indexes to one of my tables in SQL Server 2025:
ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
PRIMARY KEY (CustomerID);
-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerPhone
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disableI see this when I check the index status:
I decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact rebuildAfter I do this, what will I see for the index status? See possible answers