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
A Cloud Dependency Failure from Amazon
By Steve Jones
I went to sleep while reading a Kindle book on my phone. I know...
Deploying AI in logistics (the unfiltered version)
A conversation with Jan Laš, CIO at HOPI, about what deploying a data agent...
T-SQL Tuesday #198 Invitation: How Do You Detect Data Changes?
It's time for T-SQL Tuesday #198! This month's topic is change detection. The post T-SQL...
Forums
Bca Kcp Pembangunan Hub/Wa (08216977701)
Jl. Pembangunan I No.25A, RT.11/RW.1, Petojo Utara, Kecamatan Gambir, Kota Jakarta Pusat, Daerah Khusus...
BCA KCP Pintu Air Hub/Wa (08216977701)
Jl. Pintu Air Raya No.36 Q, Ps. Baru, Kecamatan Sawah Besar, Kota Jakarta Pusat,...
BCA KCP Gatot Subroto Hub/Wa (08216977701)
Centennial Tower, Jl. Gatot Subroto No.Kav 24-25 lantai GF unit C, Karet Semanggi, Kecamatan...
Question of the Day
Creating a JSON Document III
I have this data in a table called dbo.NFLTeams
TeamID TeamName City YearEstablished ------ -------- ---- --------------- 1 Cowboys Dallas 1960 2 Eagles Philadelphia 1933 3 Packers Green Bay 1919 4 Chiefs Kansas City 1960 5 49ers San Francisco 1946 6 Broncos Denver 1960 7 Seahawks Seattle 1976 8 Patriots New England 1960If I run this code, how many rows are returned?
SELECT TOP 2
json_objectagg('Team' : TeamName)
FROM dbo.NFLTeams;
See possible answers