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?
2018-06-25
7,283 reads
Articles
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.
2018-06-25
3,270 reads
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.
2018-06-25
2,903 reads
SQL Server Restart or Cluster Failover Notification
How to create an automatic SQL restart or failover notification.
2018-06-22 (first published: 2015-12-10)
10,321 reads
Demoing Latch Waits with Stupid Tricks
Stuffing table variables with hard-coded values to demonstrate concurrency.
2018-06-22
2,793 reads
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.
2018-06-22
2,677 reads
Converting Trace to Extended Events
A walkthrough of a conversion of a SQL Trace setup to an Extended Event session.
2018-06-21
1,675 reads
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.
2018-06-21
2,997 reads
2018-06-19
8,376 reads
Databases with MAXSIZE Set
Every DBA needs to appropriately manage database growth. No DBA wants an application to fail because the database is out of space. A database can run out of space a number of different ways. One of those ways is to set the MAXSIZE of a database. When the database grows to the MAXSIZE the database will not grow anymore and if someone tries to add more rows they will get an error saying the database is full.
2018-06-19
2,410 reads
Blogs
Getting the SQL Server MCP Server Running
By Steve Jones
If you’ve wanted a SQL Server MCP server for your databases, it’s available. The...
Introducing azsql-migration-test: Test and Validate Azure SQL Database Migrations
Introducing azsql-migration-test, a small open-source CLI that validates your Azure SQL Database migrations against...
Rambling about Data on Wheels – origins, branding, expansion
By DataOnWheels
I have been asked many times about how the name “Data on Wheels” came...
Forums
Make It Routine
Comments posted to this topic are about the item Make It Routine
DBCC CHECKDB Limits III
Comments posted to this topic are about the item DBCC CHECKDB Limits III
CROSS APPLY Fundamentals: Part 1
Comments posted to this topic are about the item CROSS APPLY Fundamentals: Part 1
Question of the Day
DBCC CHECKDB Limits III
On SQL Server 2025, does DBCC CHECKDB support Memory-Optimized tables?
See possible answers