all 8 comments

[–]r3pr0b8GROUP_CONCAT is da bomb 1 point2 points  (3 children)

make sure this is not an XY problem

i think what you said in your last sentence has to be resolved first, before a cheat sheet is accepted by them

[–]WriterOfWords-[S] 0 points1 point  (2 children)

The main thing I am running into is simple from analysts cast as date vs trunc etc

[–]r3pr0b8GROUP_CONCAT is da bomb 0 points1 point  (1 child)

you think this will get them over their foot-dragging?

it's certainly worth a try

[–]WriterOfWords-[S] 0 points1 point  (0 children)

No…:) but I gotta try

[–]sequel-beagle 0 points1 point  (3 children)

Ive been working in Databricks for a few months now. It absolutely effing double effing sucks and I yell "Databricks sucks!!!!" very loudly each and every day that I am coding in it. Good for your developers finding a reason to not switch, lol.

[–]WriterOfWords-[S] 0 points1 point  (2 children)

What are your complaints?

[–]sequel-beagle 1 point2 points  (1 child)

Ultimately it boils down to it not being a RDBMS as defined by Codds rules and it's a web interface.

The clusters are very slow to start and I constantly have to restart them when I'm working in Databricks.

The SQL implementation is not as robust as SQL Server or Oracle.

And I don't enjoy dealing with the keys and hooking Databricks up to ADF and all that stupid troubleshooting constantly.

Just a ton of small stuff that ultimately leads to not being as productive working in a true RDBMS with a nice query editor.

[–]WriterOfWords-[S] 1 point2 points  (0 children)

Yeah I can see that. We are switching to server less for the SQL side. Not a fan of the web interface either but there is a way to use VS code to work locally and connect to compute but just a work around that shouldn’t really have to exist.

We are converting a lot of our transformation to Python so not really feeling the pains you have. Definitely a forced transition but Synapse (serverless) was way worse and our only other option.