Microsoft Python Driver for SQL Server
Link: https://github.com/microsoft/mssql-python
Discussion: https://news.ycombinator.com/item?id=45277023
SQL Roadmap for 2025 - Data Analysis in Motion 
CyberTec Daily Dose Learning 
SQL vs Data Science? With both sets of powerhouses in IT working together, it is vital to understand the core concepts of each area. Here are the top 10 features of SQL in data explained.
ebokify.com/sql
ebokify.com/data-science
Enjoy !!!
Question for #datascience #Rstats #duckdb #SQL folks:
I have some MySQL dump (.sql) files from an old research project that I wasn't involved in. I want to try and resurrect the project by converting the old database to a duckdb database that I can ultimately work with in R.
Is this possible and, if so, what is the best way to do this?
I have basically zero experience with the server-client types of RDBMS, so I'm getting stuck right at the beginning (i.e. what do I actually need to do before I can "read" the .sql file into a running database?).
Any help or pointers in the right direction much appreciated.
"How to Think Like the SQL Server Engine" is live now. And it's free!
Évidemment, la refonte du site des Archives de Paris a cassé les anciens liens et ce sujet n'est pas évoqué dans le billet annonçant la refonte. Ce qui montre que la gestion des URL demeure un impensé. Faut pas oublier que le web est une toile d'araignée ! Espérons que des redirections soient prévues dans un deuxième temps.
L'occasion de refaire un peu de SQL, pour savoir combien y'a de liens dans Wikipedia : 15 026 https://quarry.wmcloud.org/query/97215
I spent the afternoon with the great interactive https://dbquacks.com/tutorial/1 tutorial, teaching me how to "struggle with and eventually write" working SQL. Lots of fun, very well thought out (and fun!) examples. Hat tip and thanks to @dailydrop.hrbrmstr.dev for pointing it out. #SQL #learning #databases
@nixCraft It's so simple to avoid terrible mistakes in interactive #SQL tools:
NEVER SWITCH ON #AUTOCOMMIT.
After any update or delete, watch your tool's response. If it's like "3,560,628 rows affected", but you expected only 1 or 5 or so, then do "rollback" instead of "commit".
Adding OR logic forced us to confront why users preferred raw SQL
Link: https://signoz.io/blog/query-builder-v5/
Discussion: https://news.ycombinator.com/item?id=45196991
#VideoGames #DOOM #SQL #stunting
'A computer scientist used only “pure SQL” to construct a multiplayer DOOM-like game. The resulting first-person shooter game, cobbled from a mere ~150 lines of Python code, is dubbed DOOMQL.'
#OpenToWork | Data Engineer | ETL & Contrôle Qualité
CV PDF : http://gabriel.chandesris.free.fr/gabysblog/docs/CVGabrielChandesris.pdf
#ETL #Python #SQL #DataQuality #BigData #Data
Prêt à optimiser vos pipelines de données !
RT plz #i4emploi #Recrutement #Emploi #DataEngineering #Spark #Scala #Java ...
Trying to persuade developers to follow best practices is a joyless endeavor.
Sure, go ahead and store formatted data as strings in a relational database.
I have no experience in this matter and I'm just being difficult for no reason. 
Building a DOOM-like multiplayer shooter in pure SQL
Link: https://cedardb.com/blog/doomql/
Discussion: https://news.ycombinator.com/item?id=45183050
#FediHire If anyone needs a database developer around the end of this year (2025) or early next year (2026), I’ll be available around then! I can work in #SQL, #VB, #C#, #SQLServer and #Snowflake.
My current contract comes to an end in mid-November and I’m very good at remote working.
On the other hand, if your role is in Gloucestershire, I’m more than happy to work onsite.
Let’s make things happen for you!
“Just use #SQL”, they say.
“No need for ORMs”, they add.
And they may be right, but… But then accidental complexity piles in.
Just is enough for a simple or explicit context. Eventually, as our system grows, we’ll need to deal with complications. Popular tools might not be perfect; they may be too heavy, depending on design decisions, but as Gerald Weinberg said:
"Things are the way they are because they got that way"
You can live “just” with something. This can be a good starting point. Yet, we should always consider when deciding on DIY or “take off the shelve” solutions where we need to land and what our main problem is to solve.
Because if it appears that we’ll need more advanced features, then we’ll follow the path similar to the one that people building popular libraries/tools have taken.
It’s always worth thinking whether “just” will be enough for us. Usually, “just” is enough only for some time. And it is better not to overlook this to change our approach, as then we can deal with accidental complexity related to wrongly weighted “just”.
How does "wrongly weighted just" look like? Check in my latest #ArchitectureWeekly edition
https://www.architecture-weekly.com/p/just-use-sql-they-say-or-on-how-accidental
What are your "wrongly weighted just" horror stories?
Database choice confession: "The only reason you use MongoDB is because you don't know SQL."
Gah! I should have quit working at 5p.
Instead, I found two database tables that store phone numbers-formatted phone numbers. And guess what? The format is different between tables.
So what does a developer do? They join the tables on phone number columns, both wrapped in a user-defined function that strips out non-digit characters.
Folks, this is all so wrong.
