github/sql-server-samples
1
0
Fork 0
mirror of https://github.com/Microsoft/sql-server-samples.git synced 2025-12-08 14:58:54 +00:00
Code Issues Releases Wiki Activity
Files
52ae8f43adc0459f78b9f761ed6d4084fd5aa6b0
sql-server-samples/samples/databases/wide-world-importers/workload-drivers/vehicle-location-insert/README.md
Jos de Bruijn 52ae8f43ad readme updates for workload drivers
2016-05-26 08:26:08 -07:00

2.8 KiB
Raw Blame History

Workload Driver for Vehicle Location Insertion in WideWorldImporters

This application simulates an insertion workload for vehicle location in the WideWorldImporters sample database.

The main purpose is to compare the performance of data insertion into traditional disk-based tables compared with memory-optimized tables. For a more comprehensive sample demonstrating the performance of In-Memory OLTP see the in-memory/ticket-reservations sample.

Contents

About this sample
Before you begin
Running the sample
Sample details
Disclaimers
Related links

About this sample

  1. Applies to: SQL Server 2016 (or higher), Azure SQL Database
  2. Key features: Core database features
  3. Workload: OLTP
  4. Programming Language: C#
  5. Authors: Greg Low, Jos de Bruijn
  6. Update history: 25 May 2016 - initial revision

Before you begin

To run this sample, you need the following prerequisites.

Software prerequisites:

  1. SQL Server 2016 (or higher) or Azure SQL Database.
  2. Visual Studio 2015.
  3. The WideWorldImporters database.

Running the sample

  1. Open the solution file MultithreadedInMemoryTableInsert.sln in Visual Studio.

  2. Build the solution.

  3. Run the app.

Sample details

This application is used to compare the insertion of rows into the OnDisk and InMemory tables in Wide World Importers. The required objects must have already been created by following the earlier steps in the demonstration script.

When executed, this application displays the following:

Alt text

Ensure that the connection string is set appropriately. It is save when the program is edited. If you ever need to set it back to the default value, open the program, clear the string, and exit the program. When you restart the program, the connection string will have been returned to the default value.

You can control the number of threads performing the insert operations. You can choose whether to insert into an on-disk table or an in-memory equivalent of the same table.

The application will periodically (about every second) display the latest execution times for each insert.

Disclaimers

The code included in this sample is not intended to be used for production purposes.

Related Links

TBD