Enable FIPS 140-2 Compliance in SQL Server
What is FIPS? How do I use it? What is going to break if I do use it?
Power BI Introduction: Working with Power BI Desktop — Part 2
Power BI Desktop is the free tool from Microsoft for developing in Power BI. In this article, Robert Sheldon walks you through importing and manipulating data with the Query Editor in Power BI Desktop.
Receive SQL Server Alerts through Slack
In this tip we look at how we can use Python and SQL Server 2017 to send alerts from SQL Server to Slack messaging service.
Common Mistakes
This week Steve Jones is wondering what the common mistakes that T-SQL developers make are.
SQL Server Restart or Cluster Failover Notification
How to create an automatic SQL restart or failover notification.
Demoing Latch Waits with Stupid Tricks
Stuffing table variables with hard-coded values to demonstrate concurrency.
In-Memory OLTP – Common Workload Patterns and Migration Considerations
In-Memory OLTP is a high performance, memory-optimized engine integrated into SQL Server 2014 and designed for modern hardware trends. In-Memory OLTP allows users to move data into memory resident tables while keeping other data in traditional, disk-based table structures. For performance critical workloads, users can also migrate Transact-SQL code to natively compiled stored procedures. This can provide additional performance gains. This paper aims to help readers understand some of the common architectural patterns where In-Memory OLTP has provided significant benefits. The paper also discusses considerations for migrating applications to In-Memory OLTP.
Converting Trace to Extended Events
A walkthrough of a conversion of a SQL Trace setup to an Extended Event session.
In-Memory OLTP – SQL Server In-Memory OLTP Internals Overview
In-Memory OLTP (project “Hekaton”) is a new database engine component, fully integrated into SQL Server. It is optimized for OLTP workloads accessing memory resident data. In-Memory OLTP allows OLTP workloads to achieve significant improvements in performance, and reduction in processing time. Tables can be declared as ‘memory optimized’ to enable In-Memory OLTP’s capabilities. Memory-optimized tables are fully transactional and can be accessed using Transact-SQL. Transact-SQL stored procedures can be compiled to machine code for further performance improvements on memory-optimized tables. The engine is designed for high concurrency and blocking is minimal.
Blogs
A New Word: on tenderhooks
By Steve Jones
on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...
Ramblings about data communities and your contributions, no excuses
By DataOnWheels
I have been active in the data community throughout my career. I have met...
SQL Server Journey till 2025 (brief)
By Vinay Thakur
Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...
Forums
how do i map the "current" object entry in for each to one variable
hi, in an ssis for each loop over an object variable called MyListVariable, i...
Simulating Mercury’s Orbital Motion Using Pure T-SQL (NASA 2025 Dataset)
SQL Server is typically viewed as a transactional or analytical database engine. However, it...
Azure SQL Database | CREATE EVENT SESSION [Blocking_Capture] ON DATABASE
Hello, Is there a way in Azure SQL Database to change the 'Blocking Process...
Question of the Day
String Similarity I
On SQL Server 2025, when I run this, what is returned?
SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL') See possible answers