If you have not done so already, create your own Enzo Server 3.1 VM in Azure from the Marketplace . To find Enzo in Azure, simply log into your Azure Portal, choose to create a new Resource, and search for Enzo. The 30-day trial edition of Enzo Server begins when the VM is first started..

It is usually best to install this VM in its own Resource Group so it is easier to manage. Just choose to create a New Resource Group during the provisioning process. Also note that this Enzo Virtual Machine runs a pre-configured Enzo Server Standard Edition, free for 30-days. While the Enzo Server license is free for 30 days, you may incur charges for hosting the VM itself in Azure. Enzo Unified is not responsible for the Azure-related costs you may incur, including but not limited to storage and compute costs. Please read the Enzo EULA carefully.

The Enzo Server VM is pre-configured with the following software and options:

• SQL Server Express Edition with SSMS (SQL Server Management Studio)
• FTP Server
• Microsoft MSMQ
• Office 365 Data Access (for accessing Excel documents)
• Enzo Server 3.1
• Google Chrome

Enzo Server is pre-loaded with the following adapters. Some adapters are already configured for use, while others require further configuration to authenticate on remote systems, such as the SharePoint adapter. The adapters that are pre-configured and available immediately upon starting the VM are marked with an asterisk (*).

• AzureBus
• AzureKeyVault
• AzureStorage
• CSV (*)
• Files (*)
• FTP
• FTP2 (*)
• HTTPEndpoint (*)
• MSMQ (*)
• Parquet (*)
• RabbitMQ
• SharePoint
• SQLServer
• XLS (*)

The Enzo Server VM comes with a few sample files so you can try some of the adapters immediately. The sample files are located under the c:\tmp\csv\, c:\tmp\parquet\ and c:\tmp\excel\ folders.

The following sample SQL files are available on the Enzo Server VM upon startup, located in the c:\init\sql\ folder:

• EnzoDemo_AZUREBUS.sql
• EnzoDemo_AzureKeyVault.sql
• EnzoDemo_AZURESTORAGE.sql
• EnzoDemo_CSV_FTP.sql
• EnzoDemo_HTTPENDPOINT.sql
• EnzoDemo_MSMQ.sql
• EnzoDemo_Parquet.sql
• EnzoDemo_SHAREPOINT.sql
• EnzoDemo_XLS.sql

For example, you can immediately query CSV files using the EnzoDemo_CSV_FTP.sql sample SQL code. A few sample CSV files are available on the virtual machine for testing purposes. Here is a sample command provided:

SELECT * FROM bsc.csv.[file@firestations] WHERE _path = 'c:\tmp\csv\usfa-registry-FL.txt'

The best way to get started with Enzo is to use SQL Server Management Studio (SSMS) 2016 or higher. This Enzo Server VM comes pre-configured with SQL Server Express Edition; a SSMS shortcut should be visible on the VM. Double-click on it to start SSMS. You will use SSMS and login directly against the Enzo Server installed on this Virtual Machine.

Start SSMS and Login to Enzo

Because Enzo Server emulates parts of the TDS protocol, you can connect to Enzo just like you would connect to a SQL Server database: by providing the IP address (or server name) and port of Enzo Server, and a login account/password. In addition, since Enzo Server emulates SQL Server, it has its own 'sa' account/password as well. Last but not least you can create additional logins using Enzo Manager, the management interface for Enzo Server.

NOTE: Active Directory accounts are supported with the Enterprise Edition of Enzo Server.

Once logged in to Enzo Server, you can start running SQL commands. Let's start with a command unique to Enzo Server: the help command. Enzo Server provides an inline help mechanism allowing you to explore what you can do. Let's discover the list of adapters that are loaded on the Enzo Server you are connected to by executing this command:

EXEC Help

By default, all commands execute against the BSC database, the default database for an Enzo Server, so the above command is equivalent to EXEC bsc.help.

You can run this command to explore the SharePoint adapter:

EXEC SharePoint.help

However, let's use the _handlers virtual table so we can use a SELECT command that we can further filter:

SELECT * FROM SharePoint._handlers

In Enzo, a handler is equivalent to an Object in SQL Server; it is usually a Stored Procedure and/or a Table. Some of the Procedures can be called as a Table using a SELECT statement providing filtering and ordering options that the Stored Procedure equivalent may not provide.

For example, the GetListItemsEx procedure found in the SharePoint adapter is the handler that can be used with an EXEC command to return list items from SharePoint. If you look at the 'SELECT' column of the _handlers output you will see 0; this means this specific handler does not support a SELECT equivalent. To figure out how to call the GetListItemsEx handler, and see what input parameters and returned columns are, run this command:

EXEC SharePoint.GetListItemsEx help

The SharePoint adater is a powerful connector for SharePoint Server and SharePoint Online, with support for a large number of operations, including managing lists, documents, users, groups, folders, and sites. The SharePoint adapter also allows accessing and managing Sub Sites and Document Lists with support for large file transfers.

Before you can use this adapter, you must configure it to access an existing SharePoint site. To configure the SharePoint adapter from SSMS, use the SharePoint._configCreate command as such:

EXEC Sharepoint._configcreate 
			'site1', 
			1, 
			'user1@mycompany.onmicrosoft.com',
			'__USER1_PASSWORD__',
			'https://mycompany.sharepoint.com/teamsite/'

Let's look at the lists handler; its Procedure and TableName are the same and it is a SELECT operator. This means we can call this handler this way:

SELECT * FROM SharePoint.lists

In order to communicate with underlying services most adapters require creating at least one configuration setting. Each login defined in Enzo Manager can optionally have one default configuration setting that will automatically be loaded when running SQL commands.

The Standard edition of Enzo Server only provides the 'sa' account

In this screenshot you can see the SharePoint configuration settings defined for the 'sa' account.

If you do not have a default configuration setting, or would like to switch the configuration setting to use during a session, use the SharePoint._configUse SQL command. Note that using Linked Server to call Enzo requires the use of a default configuration setting; using the _configUse command through Linked Server does not work.

Each adapter stores its own log information to disk in a specific directory. Enzo Manager allows you to view the current day's worth of activity log which includes successful and failed calls. To view the log, click on Environment->View Current Adapter Log