Starburst SQL Server connector#
The Starburst SQL Server Connector is an extended version of the SQL Server Connector with configuration and usage identical.
The following improvements are included:
The additional features of the connector require a valid Starburst Enterprise Presto license, unless otherwise noted.
The connector includes a number of performance improvements, detailed in the following sections.
This feature is available for free, and does not require a valid license.
The SQL Server connector supports table and column statistics to improve query processing performance based on the actual data in the data source.
The statistics are collected by SQL Server and retrieved by the connector.
The connector can use information stored in single-column statistics. SQL Server Database can automatically create column statistics for certain columns. If column statistics were not created automatically for a certain column, you can create them by executing the following statement in SQL Server Database.
CREATE STATISTICS my_statistics_name ON table_schema.table_name (column_name);
SQL Server Database routinely updates the statistics. In some cases, you may want to force statistics update (e.g. after defining new column statistics or after changing data in the table). You can do that by executing the following statement in SQL Server Database.
UPDATE STATISTICS table_schema.table_name;
Refer to SQL Server documentation for information about options, limitations and additional considerations.
Dynamic filtering is enabled by default. It causes the connector to wait for dynamic filtering to complete before starting a JDBC query.
You can disable dynamic filtering by setting the property
dynamic-filtering.enabled in your catalog properties file to
Additionally, it supports pushdown of the following aggregate functions:
Caching table projections#
The connectors supports table scan redirection to improve performance and reduce load on the data source.
The connector includes a number of security-related features, detailed in the following sections.
The SQL Server connector supports user impersonation.
User impersonation can be enabled in the catalog file:
User impersonation in SQL Server connector is based on
EXECUTE AS USER.
For more details visit: docs.microsoft.com.