this post was submitted on 18 Jun 2024
326 points (99.1% liked)

Technology

59720 readers
6095 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] NeoNachtwaechter 41 points 5 months ago (6 children)

There you can see how bad they are treating their customers, declaring end of support against their wishes and demands.

[–] [email protected] 15 points 5 months ago (1 children)

In my experience it’s normally unsupported 5 years after they released an updated version. The enterprises probably haven’t bothered to update because it requires too much time to plan, or the people responsible have long since moved on and the knowledge has been lost.

Probably not M$ being the bad guys. You can’t support ancient versions forever.

[–] Dashi 8 points 5 months ago

Very much this. I dislike M$ as much as the next guy but it isn't always their fault. The biggest reason we have outdated SQL in my experience is older software that clients do not want to pay for an upgrade for that uses a sql backend that will break if we have the databases in compatibility mode.

Just like M$ with good reason (mostly) end of life's an OS they need to no longer mainstream support older software versions.

[–] IsThisAnAI 10 points 5 months ago* (last edited 5 months ago) (2 children)

I honestly can't tell if this is sarcasm or just ignoring the many many foss projects with forced deprication.

[–] voodooattack 1 points 5 months ago

At least they can be forked if someone needs them enough.

[–] NeoNachtwaechter -4 points 5 months ago* (last edited 5 months ago) (1 children)

Are you just trying to tell me that FOSS projects usually do what their customers need?

[–] IsThisAnAI -5 points 5 months ago
[–] [email protected] 7 points 5 months ago (1 children)

All software eventually gets deprecated / unsupported, including free open source projects.

I think the update cycle on MySQL and Mongo is more aggressive than MS SQL.

The only difference is you pay for MS SQL.

[–] Semi_Hemi_Demigod 4 points 5 months ago (1 children)

There are people who pay for MySQL and Mongo. And even MariaDB. All of them have enterprise versions of their software.

[–] [email protected] 3 points 5 months ago

And how many years do they support a specific release before making you upgrade.

Looks like MySQL standard releases are one year and LTS releases are 5 or up to 8 with extended support.

So somewhat similar to Microsoft

[–] [email protected] 4 points 5 months ago (1 children)

I would say that this is a sign of a bad product. Apparently, compatibility between SQL server versions is not great.

[–] [email protected] 4 points 5 months ago (2 children)

I have never had a problem upgrading a SQL server. Granted, we aren't talking about anything fancy like database sharding, but the janky applications I work with have never complained.

[–] [email protected] 5 points 5 months ago (1 children)

I think in 99% of use cases, upgrading isn't a problem. Most of the time new SQL versions are backward compatible. I've never personally had a problem upgrading a database for a product that expects an older version.

They do have compatibility modes too, but those only go back so far too.

But, I think companies with their production databases for perhaps older complex systems are likely very weary of upgrading their working database. This is most likely where this situation comes from. Imagine being the person responsible for IT, that upgraded the DB server and database to the latest version. Everything seemed to be working fine. Then accounts run their year-end process, it falls over and now there are months of data in the newer version that won't work properly. It'd be an absolute pain to get things working again.

Much safer to leave that SQL 2005 server doing what it does best. :P

[–] Mbourgon 2 points 5 months ago

It’s not just SQL, it’s frequently the OS. Corporate tools don’t support the new OS so you install the “supported” OS, which is now several years old, and which only supports the next version or two of SQL Server. Microsoft also didn’t help things with 2012R2, which was 2 years later but had the same EOL as 2012.

And yes, you can set compatibility level on the database, but there are still edge cases where the engine version matters. And the business prioritizes, but upgrades are lower on the list than money-making features.

[–] [email protected] 2 points 5 months ago (1 children)

Apparently, it is not only my oberservation, but the article says similarly:

The inconsistent approach to backward compatibility in decades past may also have played a part.

However, I'm not a db admin and my perspective might be biased (infosec).

[–] [email protected] 2 points 5 months ago

I don't know what they're talking about there, but that might just be ignorance on my part, because I'm not a database administrator. For the basic use cases, SQL hasn't changed in decades. For simple applications you could even change from MSSQL to MariaDB to postgres and make only minor changes.

[–] capital 1 points 5 months ago

I hope this is sarcastic.

Is MS supposed to support everything in perpetuity?

[–] Cornelius_Wangenheim 0 points 5 months ago* (last edited 5 months ago) (1 children)

What? There's lots of reasons to complain about Microsft, but their legacy support is not one of them. Almost every product they make gets 10 years of support + 3 more if you pay for it. In comparison, Postgres only does 5, MySQL is 8, and Mongo is 3.

[–] [email protected] 1 points 5 months ago (1 children)

its generally just consumers on the consumer OS who have that image of Microsoft.

take for example their Xbox Division. Microsoft is the o nlu company where its possible to throw in an OG xbox game in their modern console and play it (after a compatibility patch). Both nintendo and sony couldnt even fathom that kind of backwards compatibility. Microsoft is also the one who keeps up their digital store (on console) the longest

[–] IsThisAnAI 0 points 5 months ago (1 children)

You most certainly cannot play og Xbox games on a series. 360÷ only and not all of them.

[–] [email protected] 1 points 5 months ago (1 children)
[–] IsThisAnAI -1 points 5 months ago (1 children)

There are only 60 og Xbox games and you are purchasing a separate license. You can't just use your disks from the console. Then, when you get into 360 era games you can just use the disk without repurchase (they upgrade you to a digital format as well).

[–] [email protected] 1 points 5 months ago

on the former point, i never claimed it was all disks, I only claimed that it was even remotely possible to stick a disk in and possibly play an og xbox game. Something you couldnt remotely do on the latest playstation (wouldnt boot any ps1 game) nor nintendo for obvious reasons(no disk drive, no compatibility with older cart systems)