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
Did You Really Name That Default?
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Monday Monitor Tips: A New Analysis Page
By Steve Jones
We have multiple teams (8) working on Redgate Monitor. Some work on the Standard...
Case Studies: Real-World Success Stories of FinOps Implementation
By HeyMo0sh
Learning any kind of theory is easy, but adapting FinOps and watching it rescue...
Forums
The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI
Comments posted to this topic are about the item The day-to-day pressures of a...
The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions
Comments posted to this topic are about the item The Problem Isn't Always Your...
Identity Defaults
Comments posted to this topic are about the item Identity Defaults
Question of the Day
Identity Defaults
What happens when I run this code?
CREATE TABLE dbo.IdentityTest
(
id int IDENTITY(10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
See possible answers