Tags

#database
database

3stories
3 d agolatest
Veri ve SQL Server
UTF-8 Collation Migration
CCC# Corner Vivek Kumar 3 d ago

Migrating SQL Server to UTF-8 Collations Without Breaking Data

In SQL Server 2019 and later, varchar columns using a collation whose name ends in _UTF8 can store Unicode text, so not every text column has to become nvarchar. The change is more than a single database setting, though: comparisons, sorting, unique indexes and storage sizes all shift. The article lays out a step-by-step path from column inventory to production rollout.

MySQL vs Nebula
Why graph queries stalled
DVDEV Community: #dotnet Mehdi Mohseni Oct 24

MySQL Recursive CTE vs C# BFS vs NebulaGraph at 500 Million Rows

A team moving a relationship-heavy system from MySQL to graph databases reports that a recursive CTE collapsed at around 500 million rows. The author built a reproducible benchmark comparing the CTE, a C# breadth-first search on the same MySQL tables, and NebulaGraph. The results suggest the CTE's design, not the relational engine, caused most of the delay.

SQL Server
Wrong session setting
DVDEV Community: #dotnet Kausar Raza Oct 23

SQL Server Msg 1934: why QUOTED_IDENTIFIER errors happen and how to fix them

SQL Server error 1934 appears when a statement uses a feature such as a filtered index while the session has QUOTED_IDENTIFIER off. The author explains why the ASP.NET Core application never sees it while the classic sqlcmd does, and how the setting interacts with stored procedures. Useful for anyone who updates ASP.NET Core Identity tables by hand.

Feedback

Found a bug or have an idea? Your message lands straight in my inbox.

Type of message