Skip to content
All topics

Databricks SQL

Recent items mentioning Databricks SQL across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.

60 recent items5 releases4 news43 videos8 community threads
What's happening in Databricks SQLAI synthesis · updated 9d ago

Databricks SQL is set to revolutionize real-time analytics with the introduction of Lakehouse//RT and the Raiden engine, promising millisecond performance and massive concurrency directly on lakehouse formats 1. Recent enhancements also include support for query tags to improve cost attribution and context across various tools 8, and new capabilities like incremental REPLACE WHERE flows for targeted data refreshes 4.

Generated daily from the 10 most recent items mentioning Databricks SQL. Click any [N] to jump to the source.

Databricks CommunityGenerative AI

DBSQL MCP output limit

002w ago
Databricks CommunityGenerative AI

Querying Metric Views via Classic/Pro SQL Warehouses

002w ago
Databricks CommunityTechnical Blog

Incremental REPLACE WHERE Flows Brings Targeted Refreshes to SDP and DBSQL

002w ago
Databricks CommunityAdministration & Architectureanswered

Restrict certain queries on SQL Warehouse

003w ago
Databricks CommunityData Engineering

SQL Warehouse stuck on "Cluster Start-up Delayed"

001mo ago
Databricks CommunityData Engineeringanswered

Databricks SQL connection becomes stale in long-running app

001mo ago
Databricks CommunityCommunity Articles

Databricks SQL Just Dropped Some Massive Engine Upgrades for Data Engineers

001mo ago
RedditGeneral

Debugging a Databricks Federated Query

Hi, I came across an interesting question on the Databricks Community, and I thought I would share my findings in case someone else runs into the same issue. Maybe this will help save some time debugging. The setup was as follows: * SQL Server was registered as a federated connection in Unity Catalog. * Queries were executed directly from Databricks against federated SQL Server tables. * The user who created the thread executed a query using standard date functions such as `YEAR()` and `MONTH()` against a federated table. Example of query that was executed: SELECT MONTH(order_date) AS order_month, YEAR(order_date) AS order_year, COUNT(*) AS total_orders FROM federated_db.sales.orders GROUP BY MONTH(order_date), YEAR(order_date) However, the query failed with the following error: `com.microsoft.sqlserver.jdbc.SQLServerException: 'EXTRACT' is not a recognized built-in function name. at` So, what is happening here? At first glance, this looks confusing because SQL Server does support the `YEAR()` and `MONTH()` functions. As it turns out, in Databricks SQL, `YEAR()` and `MONTH()` are synonyms for the ANSI **EXTRACT()** function. https://preview.redd.it/5grz6yvu7n3h1.png?width=765&format=png&auto=webp&s=19cb791a079ddbbe2eb696f77d1693028d0bd722 That is where the problem occurs: SQL Server does not support the ANSI `EXTRACT()` syntax, so the federated query fails. To work around this, you can try rewriting the query in a way that is compatible with the federated execution path. Alternatively, you can use the **remote\_query()** function, which allows you to run SQL directly against the external database using the native SQL syntax of the remote system. Orignal thread: [Re: Extract SQL function in SQL Server federated d... - Databricks Community - 157392](https://community.databricks.com/t5/data-engineering/extract-sql-function-in-sql-server-federated-database/m-p/157397#M54544)

50szymon_dybczak1mo ago