on
RE:
I agree with folks; this is a must-have feature in a lakehouse: the ability to easily separate the physical layer from the abstract layer without constantly copying or materializing data.Use case examples:Rapidly profile and explore raw data (CSV, JSON, etc.) in the lakehouse/files using T-SQL/SQL OPENROWSET in SQL ENDPOINT.MVVM style design pattern: Implement an interface (view) on top of raw data files (CSV, JSON, etc.) in SQL ENDPOINT using OPENROWSET to facilitate downstream data flows/ETLde-serialize and standardize json schema easily in a view using OPENROWSET and OPENJSONexpose data in a "fast track mode" to consumer So basically, just reply with the Synapse Serverless feature. ;-)Furthermore, it says that this idea is in "Planned" status, so can we get an ETA on it? This information could be very helpful in preparing our migration plan from Synapse to Fabric (or not).Thanks! :-)
RE:
I need this badly! My legends are routinely 20+ items and when you mouse over a point in a graph it actually isn't showing the point you are hovering over, so you need to be able to scroll to the right one! And/or make it show the one you are hovering over first!Right now the only way to get "more lines" in a tooltip box is to make the font of tooltip 8.
RE:
https://cactussuppliers.com/
RE:
Our Peyote Cactus for sale is cultivated with the utmost care and respect for its cultural significance. Each cactus is grown in optimal conditions, ensuring that it thrives and develops the rich alkaloid content that makes it so sought after. We take pride in offering only the highest quality Peyote, harvested sustainably and ethically, so you can experience its profound effects without compromising the environment or the traditions it represents.peyote cactus for sale | mescaline for sale | buy mescaline online
RE:
Needed to generate ROI for the usage of M365 and Teams Applicaions.
RE:
Any updates here?
RE:
I find this absurd that this has not been addressed yet. This is especially annoying for developers that put their objects in groups and need to multi click multiple times to get to the correct object. I am not exaggerating when I say I have accidentally triggered this "feature" well over a thousand times over the past 4 years. The idea to force this on a double click was a horrendous idea to start, and to not fix it after 4 years is beyond incompetence.
RE:
The current workaround of duplicating columns is not efficient for maintenance. This feature is very much needed
RE:
Found that this was isolated to the customers environment and was being unallocated during a custom reconcile procedure. This can be closed.