February 19, 2024 at 9:02 pm
When it comes to programming and how robust / flexible the programming can be with SQL Server - have experienced a lot what all can be accomplished with how we convert any logic to a working functionality . I am here to understand what are other database technologies which are available who can be the actual competitor .
As it depends upon how you are going to use this database to function - will have an high-level details on how we are using it .
There are actually more to talk but will stop here - trying to understand who is the actual competitor who can do all these stuff in one place . People are talking about microservices - yes it's really good but will it fit the need is bigger question which i have .
Breaking a complex structure into microservices who can work on it's own - it's great to hear but is it that easy .
Any information on PostgreSQL being named as replacement - please share more details how this is considered .. apart from any other new tech stack .
All is to understand - research and upgrade . thanks for the responses .
February 20, 2024 at 1:50 am
IMHO, the only "actual competitor" is ... the people writing the code.
If they not so good at SQL Server, the code is going to be slow. What makes you think they're suddenly going to be able to write much faster code if they change to another relational engine? And, remember, SQL <> SQL once you get beyond the basics and sometimes even before the basic. For example (I don't know if it's changed in the last 15 years), the UPDATE statement in Oracle didn't have a FROM clause whereas SQL Server has always had an UPDATE with a FROM clause.
None of the stuff you posted sounds difficult. If you're having performance issues, perhaps you folks need to get some good schooling on performance. Changing to Postgre, MySql, Oracle, whatever, isn't going to magically provide performance. You still need to write high performance code.
And, no... none of that is meant as a slam. People just don't know what they don't know. Get some help with some of your issues. Changing the the pot the poison is in isn't going to make it less poisonous. Sometimes, you have to know how "cook the beans" to make them less poisonous and more flavorful. As a good cook will tell you, you also need to know the difference between tonka beans and vanilla beans. The same holds true with coding methods.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2024 at 2:20 am
Thanks for your response .. Reason which I am posting the questions here is that .. its not because there are issues with performance or the cases that are specified - just to give an understanding the purpose ( not some tool which does an extract and validate the data - just to give a sense ) . It's for me to understand what is the difference other's are bringing to the table or telling things that they can bring theses as selling point or which is making the industry to go towards new tech stack and call SQL Server has a "Legacy" .
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply