Articles

External Article

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

External Article

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

External Article

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

External Article

Hyper-V and PowerShell: Shielded Virtual Machines

In Windows Server 2016, Microsoft have implemented a strong security concept called Shielded Virtual Machines. Shielded VMs have been improved in the Windows Server 2019 release. In the second part of this series, Nicolas describes what Shielded Virtual Machines are and how to configure them using PowerShell.

2018-06-18

2,979 reads

Blogs

How to Connect to SQL Server When Nothing Else Works – DAC

By

It's 2 AM. Your phone is going off. Users can't connect to the application,...

Get a Range of Sequence Values: #SQLNewBlogger

By

I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...

The Agent Era: When “How do I…?” Replaces “Where do I click?”

By

After a year away getting to grips with AI and its application across the...

Read the latest Blogs

Forums

Are luxury packages in Andaman suitable for a honeymoon?

By andamantourtravelpackage

Yes, luxury packages in Andaman are highly popular among honeymooners due to their romantic...

Hiring: Financial SQL Systems Administrator

By Tracy Rivers

Fisher Phillips is looking for a Financial Systems Administrator to help support and improve our financial...

Job Opening for ERP Systems Administrator - Hybrid

By rdr1

Employee owned company, been around for over 50 years. Hybrid opportunity, looking folks in Pacific...

Visit the forum

Question of the Day

Creating a JSON Document II

I want to create a JSON document that contains data from this table:

TeamID TeamNameCity         YearEstablished
1      Cowboys  Dallas       1960
2      Eagles   Philadelphia 1933
3      Packers  Green Bay    1919
4      Chiefs   Kansas City  1960
If I run this code, what document(s) is/are returned?
SELECT json_objectagg( n.city : n.TeamName)
FROM dbo.NFLTeams;

See possible answers