- TOOLBOX FOR KEYNOTE REVIEW UPDATE
- TOOLBOX FOR KEYNOTE REVIEW FULL
- TOOLBOX FOR KEYNOTE REVIEW REGISTRATION
- TOOLBOX FOR KEYNOTE REVIEW SERIES
The language is stable, the product is stable, and I don’t have to tell clients to keep changing the way they access the database. I feel sorry for folks who have to sell Microsoft data warehousing with a straight face: before the deployment finishes, the product’s already been “reinvented” again.Īt the same time, I’m also so happy to be working in the relational database space. From DATAllegro to Parallel Data Warehouse to Hadoop to Analytics Platform System to Azure SQL Data Warehouse to Azure Synapse Analytics to Big Data Clusters, there’s something broken about the leadership vision here. Optimized locking is now available in all DTU and vCore service tiers, including provisioned and serverless.”Ĩ:58AM: Analysis thoughts on reading the Github checkins so far: this looks like yet another iteration of Microsoft’s data warehousing strategy that just can’t maintain focus for 3 years straight. This fundamentally improves concurrency and lowers lock memory.
TOOLBOX FOR KEYNOTE REVIEW UPDATE
Either data warehousing experience exposes data to analysis and reporting tools using T-SQL/TDS end-point.”Ĩ:54AM: From the documentation update list: “Optimized locking available in Hyperscale – Optimized locking is a new Database Engine capability that offers an improved locking mechanism that reduces lock memory consumption and blocking amongst concurrent transactions.
TOOLBOX FOR KEYNOTE REVIEW FULL
A Synapse Data Warehouse or Fabric Warehouse provides a ‘traditional’ data warehouse and supports the full transactional T-SQL capabilities you would expect from an enterprise data warehouse. Each Lakehouse automatically includes a SQL Endpoint to enable data engineers to access a relational layer on top of physical data in the Lakehouse, thanks to automatic schema discovery. Still stuck at 100 MB/sec throughput on the log file though, and even worse, it maxes out at 130MB/sec across the entire pool.Ĩ:49AM: From the new documentation: Fabric Data Warehouse “provides two distinct data warehousing experiences.
TOOLBOX FOR KEYNOTE REVIEW SERIES
Each Hyperscale elastic pool supports up to 25 databases on standard series hardware, max 100TB data in the pool.
TOOLBOX FOR KEYNOTE REVIEW REGISTRATION
You can join me, but to do it, you’ll need a free registration for Build, so head over there now before the keynote starts at 9AM Pacific.Ĩ:45AM: Based on this morning’s check-ins, looks like they’ll be announcing Hyperscale databases in elastic pools. If you’re bored before the keynote, you can go through this morning’s Github checkin for the Build event. Yes, those would be new products, and yes, Microsoft already has something called Fabric, but this is different.
The first bits of news are already starting to trickle out: this morning, the SSMS release notes were updated to mention Microsoft Fabric SQL Endpoint and Fabric Data Warehouse. Refresh this page starting at 9AM Pacific, noon Eastern, to see my thoughts on news as it comes out. I’m at home in Vegas, attending virtually, and I’ll live-blog the keynote.
This year, it’s a hybrid event, both in-person in Seattle and online. I’ve never attended Build in person before because the data part of the event tends to be fairly thin, and the releases for Azure SQL DB and SQL Server aren’t usually tied to Build’s dates.
Goooood morning, party people! Today is the opening day of the annual Microsoft Build conference, an event focused on people like developers and power users who build things with Microsoft tools.
0 kommentar(er)
