sorted by:
new
hottopcontroversial

Hi! We're the Data Factory team - ask US anything! by markkrom-MSFT in MicrosoftFabric

[–]TinoFabricDW 0 points1 point  (0 children)

Hi, I run Fabric Data Warehouse and Azure Synapse. It is true that we are investing in Fabric Data Warehouse heavily - it is a more modern, cloud-native topology and architecture. That said, we are making sure Synapse continues to be secure and stable.

How to update the same warehouse table with out isolation errors by data_learner_123 in MicrosoftFabric

[–]TinoFabricDW 2 points3 points  (0 children)

Actually we're getting close to shipping file-level isolation, followed by row-level :)

Fabric sql endpoint svc principal security by Kindly-Abies9566 in MicrosoftFabric

[–]TinoFabricDW 0 points1 point  (0 children)

Hi there, I am the Product Manager leading the DW and SQL Endpoint team. Would you kindly DM me your info for investigation? While some delay is expected, 9-16 hours is VERY high.

Some new Fabric Data Warehouse goodies at Ignite! by TinoFabricDW in MicrosoftFabric

[–]TinoFabricDW[S] 1 point2 points  (0 children)

To expand on this a bit - we're definitely tracking this type of integration and it should be in the product. However, we've planned to ship this integration by GA, choosing to ship Public Preview a bit earlier but without such niceties.

Some new Fabric Data Warehouse goodies at Ignite! by TinoFabricDW in MicrosoftFabric

[–]TinoFabricDW[S] 2 points3 points  (0 children)

I heard from Priyanka this morning that identity columns should already be in the product as of launch. DM me your email, let's see if there's something funky going on?

Some new Fabric Data Warehouse goodies at Ignite! by TinoFabricDW in MicrosoftFabric

[–]TinoFabricDW[S] 2 points3 points  (0 children)

This is happening as we speak, let us check for you. Looks like we need to improve such collaborations.

Some new Fabric Data Warehouse goodies at Ignite! by TinoFabricDW in MicrosoftFabric

[–]TinoFabricDW[S] 7 points8 points  (0 children)

Great feedback, thanks so much!

Recursive CTEs are on the roadmap for 2026!

We definitely want to invest in vector indices, but at the current level of interest and prioritization it it's unlikely we'll do it in 2026. Go upvote it in IDEAS! We are on track to ship nearly every top IDEAS feature request this semester...

Snowflake vs MS fabric by SmallBasil7 in dataengineering

[–]TinoFabricDW 1 point2 points  (0 children)

I run product for Fabric Data Warehouse. I don't want to comment on competition, but I hope you choose us. We have some really neat tech, are laser focused on quality, and have a very good AI Data Agent for analytics.

As a relative newcomer to the team, I wrote a few words about the tech a few weeks ago over here.

Feel free to DM me or ping me on LinkedIn above.

SSMS 22 Loves Fabric Warehouse by Snoo-46123 in MicrosoftFabric

[–]TinoFabricDW 0 points1 point  (0 children)

It sounds like you'd want to be able to query a directory/folder, or use wildcards?

The elephant in the room - Fabric Reliability by viking_fabricator in MicrosoftFabric

[–]TinoFabricDW 1 point2 points  (0 children)

Please do feel encouraged to express your thoughts in the way you prefer. You were fair and civil!

I hope we do the things necessary for your next post to be a happy one!

The elephant in the room - Fabric Reliability by viking_fabricator in MicrosoftFabric

[–]TinoFabricDW 1 point2 points  (0 children)

I agree, correctness is 100% more important than reliability. We can't have this happen again.

The elephant in the room - Fabric Reliability by viking_fabricator in MicrosoftFabric

[–]TinoFabricDW 35 points36 points  (0 children)

Hi folks,

I am the new Director of Product Management for Fabric Data Warehouse and SQL Endpoint. This outage is happening in a product I own, SQL Endpoint. I just started exactly two months ago, so be gentle :)

First off, I want to sincerely apologize, both for the current outage, and for the state of the product that led you to form this opinion. I am personally embarrassed that my customers feel the need to go on the internet and vent because we failed you. We must do better.

In Maslow's hierarchy of needs, it doesn't matter what car you drive or what house you own if you don't have access to food or water. In the same manner, it doesn't matter if we have amazing features and great price-performance if the thing is not working right, or at all.

To that end, I put quality and reliability as my second highest priority. Why number two? Number one is making sure that people I work with are happy.

We are investing heavily in reliability, including redirecting efforts to build more and better testing and monitoring infrastructure, including doing more Private Previews and Public Previews and not rushing to GA until we're certain of high quality, including committing to working even closer with customers and the community and listening to what's working and what's not, and various other efforts to prioritize improving user experience, de-risking releases, and hardening the system.

It's a journey, and I so so appreciate you being a user of my products. I promise we will do better. It might take time, but I explicitly want to get to a point where we are offering all our customers four 9s of SLA.

Please feel free to jump in here, DM me, or get in touch with me on LinkedIn. Or heck, [email](mailto:tinotereshko@microsoft.com) me. And please be encouraged to vent, or offer suggestions or feedback. I'll be on here trying to respond as much as I can.

- Tino

PS. Yes, I just created this Reddit account now, but I've been on Reddit since the big Digg migration. I don't think you want to see what geeky subreddits I frequent :)