Additional Articles


External Article

Detecting Data Breaches

Data breaches make the news on an almost daily basis. There is no turning back, however, as we are firmly entrenched in this digital way of life. Brian Kelley discusses some of the reasons data breaches occur and what we can do to prevent them.

2018-06-26

3,121 reads

External Article

Optimizing Your Query Plans with the SQL Server 2014 Cardinality Estimator

SQL Server 2014 introduces the first major redesign of the SQL Server Query Optimizer cardinality estimation process since version 7.0. The goal for the redesign was to improve accuracy, consistency and supportability of key areas within the cardinality estimation process, ultimately affecting average query execution plan quality and associated workload performance. This paper provides an overview of the primary changes made to the cardinality estimator functionality by the Microsoft query processor team, covering how to enable and disable the new cardinality estimator behavior, and showing how to troubleshoot plan-quality regressions if and when they occur.

2018-06-26

2,974 reads

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

Blogs

Github Copilot in SSMS can include data in its memory, simple prompt injections ahead

By

SQL Server Management Studio (SSMS) has recently added support for Github Copilot. This is...

Advice I Like: Failure

By

If it fails where you thought it would fail that is not a failure....

Logged in as a member of an Azure AD Group Error while Deploying DACPAC

By

Quite a long title for a short blog post ??While deploying a DACPAC (from...

Read the latest Blogs

Forums

Don't Create Workslop

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Don't Create Workslop

What is the original database name?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is the original database...

The DBScan algorithm tutorial

By Daniel Calbimonte

Comments posted to this topic are about the item The DBScan algorithm tutorial

Visit the forum

Question of the Day

What is the original database name?

What is returned when this code is run?

SELECT ORIGINAL_DB_NAME()

See possible answers