2024-10-09
314 reads
In-Memory OLTP Tables
2024-10-02
398 reads
Converting a Database to In-Memory OLTP
In-Memory OLTP was introduced with SQL Server 2014 as a way to improve transaction performance. There are several scenarios that are not supported, such as some data types, and Darko Martinovic describes the issues and provides workarounds. He also has provided a tool to assist in migrating disk-based tables to In-Memory optimized tables.
2018-06-11
3,363 reads
Microsoft IT: A Case Study on “Hekaton” against RPM – SQL Server 2014 CTP1
This paper shares the approach used to understand and determine: 1) Using ‘Hekaton’ in SQL Server 2014 against RPM, including performance analysis. 2)
Understand the specifics involved while migrating to Hekaton.
2017-08-09
3,784 reads
2017-03-24
996 reads
2016-10-06
1,039 reads
Blogs
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Advice I Like: In 100 Years
By Steve Jones
In 100 years a lot of what we take to be true now will...
Forums
is it true we cant debug c# scripts in ssis anymore under vs
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
Missing the Jaro Winkler Distance
Comments posted to this topic are about the item Missing the Jaro Winkler Distance
Question of the Day
Missing the Jaro Winkler Distance
I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:
SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.What is wrong? See possible answers