Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "Once the ASA job is created, in the Solution Explorer, the job topology folder structure could be viewed as Inputs (job input), Outputs (job output), JobConfig.json, Script.asaql (Stream Analytics Query file), Azure Functions (optional), and so on."

A block of code is set as follows:

Select input.vin, BlobSource.Model, input.timestamp, input.outsideTemperature, 
input.engineTemperature, input.speed, input.fuel, input.engineoil, 
input.tirepressure, input.odometer, input.city, input.accelerator_pedal_position, 
input.parking_brake_status,
input.headlamp_status, input.brake_pedal_status, 
input.transmission_gear_position, input.ignition_status, 
input.windshield_wiper_status, input.abs into output from input join BlobSource 
on input.vin = BlobSource.VI

New terms and important words are shown in bold.

Words that you see on the screen, for example, in menus or dialogue boxes, appear in the text like this: "To run the Stream Analytics job query locally, first select Add Local Input by right-clicking on the ASA project in VS Solution Explorer, and choose to Add Local Input."

Warnings or important notes appear like this.

Tips and tricks appear like this.