Greg Baldini @[email protected]

@notaboutthecell Obligatory reference: folklore.org/Negative_2000_… And, popularly attributed to Bill Gates: "Measuring programming progress by lines of code is like measuring aircraft building progress by weight."

@RuiRomano @KNPBI No issues here. I honestly expect this sort of thing from preview features. Just sharing the error and workaround for others hitting the same thing.

@KNPBI @GregBaldini Sorry to hear about your bad experience. We are working on the GA readiness of the PBIP format and have tried to make these required file format changes as smooth as possible. Are you still experiencing issues with the upgrade?

Upgrading from #PowerBI Desktop March '24 to April '24 (and future releases?) and using PBIP format? Watch out for a file extension that changed from 'definition.pbidataset' to 'definition.pbism'. March and prior use the former, and April the latter. March can't open April PBIPs

@SQLGene Sounds like a good primer q:

😬

@KNPBI Sync binds repo structure and branch management to the deployment environment. Build+deploy steps are basically non-existent with sync. Most ci/cd tooling and approaches are built around being able to build from a commit. Sync means that your commit must hold built artifacts.

@GregBaldini I think I understand your point but can you elaborate or link to a relevant article that does?

@KNPBI Sync is the wrong model. This is a minor piece of evidence supporting that.

@GregBaldini And it's even worse if you're using Git integration. Ask me how I know. 😡 twitter.com/KNPBI/status/1…

@NYCGuy1463 @ehansalytics Not particularly serious. A preview feature has a minor breaking change b/t versions. You should expect this Solution: Only collaborate on PBIP with the same Desktop version Workaround: Rename the .pbism to .pbidataset if your Desktop is old. The extension changed, nothing else

@GregBaldini @ehansalytics This sounds serious. Is it? Workaround ?

𝗗𝗶𝗿𝗲𝗰𝘁 𝗟𝗮𝗸𝗲 𝘃𝘀. 𝗜𝗺𝗽𝗼𝗿𝘁 𝗺𝗼𝗱𝗲 𝗶𝗻 𝗣𝗼𝘄𝗲𝗿 𝗕𝗜 What is the right choice between Direct Lake and Import mode in Power BI? #powerbi #vertipaq #directlake #import sqlbi.com/blog/marco/202…

@tpnRel1 Just read the GUID q:

This new window allows you to create a report with the same name as a report already in the workspace. Then there will really be two identical reports 🤣. 🙏 can we get an overwrite option or an indication that this name has already been used? #MicrosoftFabric

Ulalalaaa new SAVE A COPY window for #PowerBI Reports.

Security vulnerability in #SSH #openssh on #linux Affected distros definitely include Fedora 41 and Rawhide and Debian testing and Debian sid. Report and distro info below. openwall.com/lists/oss-secu… redhat.com/en/blog/urgent… lists.debian.org/debian-securit… CVE: cve.mitre.org/cgi-bin/cvenam…

Tabular Editor <3 Tabular Tools <3 Fabric!

@SQLGene @igocrite @mim_djo @alexdupler Thank you!

@GregBaldini @igocrite @mim_djo @alexdupler So quick context setting would help I think, like "Quick note on that" "Mild tangent" "Interesting fact about that" You are very detailed and precise, so it's not always clear if you are making a meta-commentary, refuting a specific point, or engaging in debate. 2/2

Notice something about #Fabric, people seems to confuse Encoding with compression, Vorder help you get you better encoding, which ultimately get you better compression. But light compression like Snappy is probably a better option

@SQLGene @igocrite @mim_djo @alexdupler I mean, the statement was "cost of CU is higher than cost of storage." I feel as if this is a pretty direct statement to reply to. Honest question: is it a Twitter norm to not reply to a specific point in a thread, but only to the root?

@igocrite @GregBaldini @mim_djo @alexdupler Thank goodness he doesn't charge tuition

@mim_djo @alexdupler I was replying to the idea of comparing cost of storage and cost of compute. They aren't directly comparable. But people use a lot of terms interchangeably that they shouldn't. I agree with you fighting the good fight, there!

@GregBaldini @alexdupler Greg, can you just read a tweet before replying 😁 all what I am saying encoding and file compression ( snappy, Gzip etc) are two different thing, people seems to use them interchangeably

@mim_djo @alexdupler Append-only, read-rarely, long retention: probably wirth spending some up-front compute to minimize data size. Update-often, read-rarely, transient data: probably worth it to optimize write time a lot. Less extreme? It depends on the things above. Do some math (:

@mim_djo @alexdupler They are not quite comparable, or at least not simply. I pay for storage for $RETENTION_PERIOD time, and pay for compute for $QUERY_TIME Smaller data can be processed more quickly, so I can race to turn off capacity faster Also depends on data change rate and write patterns

@SQLGene Take that, computers!

@GregBaldini My brain's Autocorrect caught it and fixed it

Today I learned you can make recursive slides.

@SQLGene Ehh, autocorrect is still incapable of realizing I am just as likely to write "turing" as "turning" (and more likely the former when what I am linking also says that!). I am not feeling too confident in computation today q:

@GregBaldini Maybe we can use it to solve the halting problem.

@wynhopkins May you know twice as much when you've been learning for half a century!

Regarding the size of the product and amount to learn in #PowerBI and Fabric: It's not so much Software-as-a-Service as it is Analytics-Stack-as-a-Service. No one is a deep expert on all layers of a stack. Don't feel bad if you don't know it all. No one does.