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.
Release Wednesday
One of the teams at Red Gate is releasing new changes every Wednesday, which reminds Steve Jones of a time earlier in his career.
After Six Months On The Job What Challenges Remain?
Today we have a guest editorial from Andy Warren that asks what you might do when you get settled at a new job.
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.
Jobs You Wouldn't Expect To Be Threatened By Tech But Are
Will there be a fair balance between the coming generations of technology and the human workforce? Here is a list of industries that may not think yes.
Blogs
No Shortcuts for the SQLCMD Batch Terminator: #SQLNewBlogger
By Steve Jones
I was messing around with SQLCMD and I realized something I hadn’t known. I’ve...
Where Is My SQL Agent? Running Scheduled Jobs Against Azure SQL Database
By gbargsley
One of the first things I review when I inherit a new SQL Server...
AgentDBA vs Critical SQL Server
By Arun Sirpal
It’s 07:43. Someone’s already left a message. “Something’s wrong with the DB server.” You...
Forums
Increment a number in a SQL Query based on a value
I have an issue where I have a Bill of Material list of items...
Follow Your Hunch
Comments posted to this topic are about the item Follow Your Hunch
What Happens When You Ask a Local AI to Query Your Database?
Comments posted to this topic are about the item What Happens When You Ask...
Question of the Day
Detecting Characters
I have a SQL Server 2022 English default installation on a server. I want to detect if there are any upper case characters in rows and I have this code:
SELECT CustomerNameID,
CustomerName
FROM dbo.CustomerName
WHERE CustomerName = LOWER(CustomerName)
Here is the sample data I am testing with:
CustomerNameID CustomerName 1 John Smith 2 Sarah Johnson 3 MICHAEL WILLIAMS 4 JENNIFER BROWN 5 david jones 6 emily davis 7 Robert Miller 8 LISA WILSON 9 christopher moore 10 Amanda TaylorHow many rows are returned? See possible answers