@mim_djo @philosophicles Something called "oneLake compute" however is interactive, which is where all the overloads happen in my experience unless you've got extremely inefficient datasets. Do not know what activity generates those yet
@mim_djo @philosophicles Looks like notebook runs and the lakehouse cpu they use are both background operations, which is great because they are spread over a 24 hour period like dataset refreshes. The metrics app shows an "operation id" for these but unsure where we can get history of we need to QA
@PawarBI@PowerBITips@KratosBi Can finally just make a report that shows what is off and on instead of answering the constant "are service principals enabled in our tenant" questions
Anyone interested in collaborating on a Fabric Admin API notebook to make delta tables in a lakehouse out of the API payloads? https://t.co/W0YwqDGFa0 @PawarBI@tpnRel1@JKerski
@pswider@andrewbrust I don't think anyone is arguing there isn't a lot of databricks in fabric. But if you don't think this is a big leap in capabilities for biz analysts who use PBI premium today, you do you. Not everyone can just spin up a databricks instance without jumping through hoops first
@pswider@andrewbrust I think there's been a lot of hyperbole today for sure, but I dunno, pbi and sql server reading an open source format natively seems like a big deal to me. Same with what's basically a onedrive client for a lakehouse
@pswider@andrewbrust No, pbi cannot read delta from databricks natively. It has to import and store in proprietary vertipaq format or use inefficient directquery