September 27, 2024 at 12:00 am
Comments posted to this topic are about the item Dead to Me
September 27, 2024 at 9:44 am
IT DEPENDS !
Database mirroring is not dead yet! ( Such a shame Microsoft uses that terminology now in its cloud context )
It still works and in some cases outperforms AG's !
SQLServer has so many technologies built in, you cannot use them all every now and then.
e.g. My devs don't use SSIS ( refuse to ... )
That doesn't mean these features are dead.
What would be 'saved' if MS removed "legacy cardinality estimator" ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 27, 2024 at 12:47 pm
When you mentioned over source control systems than Git, it reminded me at one of my early employers (can't remember which) we used to use MS Visual SourceSafe. That is long dead.
Digital cameras are great because no one needs them anymore, you can find old, good ones for cheap and give them to little kids as gifts. My kiddos love them.
Be still, and know that I am God - Psalm 46:10
September 27, 2024 at 2:26 pm
If you are designing a new object with DML triggers, especially nested or recursive enabled triggers, then you should take a step back and consider if there is a better solution, like encapsulating the logic in a single stored procedure or leveraging SQL Audit as an alternative to DDL triggers.
At least in my observable universe, I've seen DML triggers as the source for a lot of performance bottlenecks and deadlocking events. RCSI can mitigate it sometimes, but often it can't be resolved without refactoring the application or writing new code.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
September 27, 2024 at 2:56 pm
Like everyone who subscribes to SSC, there are a lot of technologies I consider to be dead. Or at least dead to me.
Like @david.Gugg, I used Visual SourceSafe back in my old job. I thought it was great, but then again I worked off campus with one or two coworkers, and let's be honest, we didn't know any better.
Along those lines I now consider TFS, specifically TFVC, to be a dead technology. OK, dead to me. Microsoft still supports TFS/TFVC and probably will for years to come, because there are companies out there which have devoted years of effort into TFS (now known as Azure DevOps Services/Server) with TFVC. But I got so tired of supporting something which for my current position only added aggravation to everything and everyone who had to deal with it, that I am glad it is mostly gone. (Yeah, we still have it in-house, but its use is greatly reduced.)
I could mention several more, but I'll end my contribution here with two other development technologies which are dead, at least to me. In the late 1990's when the Internet was on its inevitable match to become a massive technology/paradigm that it has become, there were millions of Microsoft developers, like myself, who had been writing applications using VB6 or Visual InterDev (does anyone remember that last one?). Microsoft saw that they had to move with the times and bring along all those VB6 developers as well. Their answer, in the early 2000's was WebForms. WebForms came at the perfect time, for all those millions of VB6 developers who were used to dragging a button onto a WinForm, dropping it, then double clicking it to bring up the ButtonClicked event to write code. It hide the shift in paradigm from us, but made it possible for us to be productive, quickly. However, WebForms' day has passed. Even Microsoft put the nail in the proverbial coffin of WebForms by not bringing it forward into .NET Core. Of course there's lots of WebForms apps still in existence today, but they're all on life-support.
The last one is VB6. Microsoft came up with Visual Basic to help those developers who had a hard time grokking C++ for Windows development. I don't know what the first version of VB was, as I didn't get involved with it until VB4, briefly. And certainly a lot of those C++ Windows developers made fun of those of us who developed Windows apps using VB, saying that VB wasn't a real programming language. Yes, we couldn't code a Fast Fourier Transform app in VB, but WOW could we get a general purpose CRUD app up and running fast. That resulted in all those millions of VB developers. But VB's day has, at least in my experience, gone. I don't even have the VB6 IDE installed on my dev box, and I've no intention of ever installing it. However, I will note that Microsoft still includes the VB6 runtime in every new version of Windows they release.
Kindest Regards, Rod Connect with me on LinkedIn.
September 27, 2024 at 3:19 pm
IT DEPENDS !
Database mirroring is not dead yet! ( Such a shame Microsoft uses that terminology now in its cloud context ) It still works and in some cases outperforms AG's !
SQLServer has so many technologies built in, you cannot use them all every now and then. e.g. My devs don't use SSIS ( refuse to ... ) That doesn't mean these features are dead.
What would be 'saved' if MS removed "legacy cardinality estimator" ?
Ha, DM is dead to me. I'd never use it, esp as MS won't support it in new work. Personally I wish they'd remove the legacy CA as well, older code and it would put pressure on them to improve the performance of the new one (or make 3.0)
September 27, 2024 at 3:25 pm
When you mentioned over source control systems than Git, it reminded me at one of my early employers (can't remember which) we used to use MS Visual SourceSafe. That is long dead.
Digital cameras are great because no one needs them anymore, you can find old, good ones for cheap and give them to little kids as gifts. My kiddos love them.
I do see cameras for kids. All of my old ones are dead, some even using charging cords I can't find.
VSS is definitely dead. I liked a lot of things about it, but it was too unstable. Had to restore it a few times and glad to leave it behind.
September 27, 2024 at 3:29 pm
If you are designing a new object with DML triggers, especially nested or recursive enabled triggers, then you should take a step back and consider if there is a better solution, like encapsulating the logic in a single stored procedure or leveraging SQL Audit as an alternative to DDL triggers.
At least in my observable universe, I've seen DML triggers as the source for a lot of performance bottlenecks and deadlocking events. RCSI can mitigate it sometimes, but often it can't be resolved without refactoring the application or writing new code.
I avoid triggers like the plague. There are places they are needed, but most of the time I don't want them, and I certainly don't want recursive ones.
September 27, 2024 at 3:31 pm
Like everyone who subscribes to SSC, there are a lot of technologies I consider to be dead. Or at least dead to me.
...
I'd agree with this. VB is really dead to me at this point. Anything in VB, I'd look to refactor into something else or add code from C# or another language instead of trying to keep it going forward.
September 27, 2024 at 4:06 pm
...
The last one is VB6. Microsoft came up with Visual Basic to help those developers who had a hard time grokking C++ for Windows development. I don't know what the first version of VB was, as I didn't get involved with it until VB4, briefly. And certainly a lot of those C++ Windows developers made fun of those of us who developed Windows apps using VB, saying that VB wasn't a real programming language. Yes, we couldn't code a Fast Fourier Transform app in VB, but WOW could we get a general purpose CRUD app up and running fast. That resulted in all those millions of VB developers. But VB's day has, at least in my experience, gone. I don't even have the VB6 IDE installed on my dev box, and I've no intention of ever installing it. However, I will note that Microsoft still includes the VB6 runtime in every new version of Windows they release.
I remember back in 1999, a recruiter scoffed at my VB6 experience and said: VB is dead and ASP (the original) was the new VB.
So, I pivoted and specialized in SQL Server development. Over the past 25 years, I've witnessed (from a distance) a lot of different app development frameworks come and go, but SQL Server is still going stronger than ever.
Actually, I still see VB6 today on occasion.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
September 27, 2024 at 6:12 pm
It's as popular as ever but I've always found JavaScript difficult to work with. With JavaScript it's like you're inventing everything whereas with SQL and other languages it seems more like engineering. As for dead it seems very few tech ever really perish. I thought MS Access and VB/VBA where dead to me but then did a project with them about 5 years ago. Going really far back I used to work with a SQL-like reporting language called Focus from Information Builders. The company was bought and the language is long gone afaik
Aus dem Paradies, das Cantor uns geschaffen, soll uns niemand vertreiben können
September 27, 2024 at 11:26 pm
There are so many dead-to-me technologies, though as others have said, most live on in some form for some users.
SQL Server Reporting Services (SSRS) is dead to me. The last thing I did with it was migrate SSRS reports to Power BI as part of a data warehouse migration from on-prem to Azure a few years ago.
Python has largely replaced Perl as a data wrangling language.
Power BI seems to have overtaken SQL Server Analysis Services (SSAS) in popularity, though I know there are still plenty of SSAS (both tabular and multidimensional) deployments still going strong.
Extended Events has replaced Profiler despite some users hanging onto the latter 🙂
September 29, 2024 at 9:23 am
Master Data Services. I've had a few goes at that in my time and it rarely ended well.
CD players and all hard-copy music. I stream all my music now.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
September 29, 2024 at 1:49 pm
There are so many dead-to-me technologies, though as others have said, most live on in some form for some users.
SQL Server Reporting Services (SSRS) is dead to me. The last thing I did with it was migrate SSRS reports to Power BI as part of a data warehouse migration from on-prem to Azure a few years ago.
<snip />
We still have a lot of SSRS at work. Heck, we've got a lot of older Crystal Reports, too. But I wanted to ask you, is it hard to convert a SSRS report to Power BI? I've seen Power BI in demonstrations, but I've never used it. And some people I've worked with have given me the impression that Power BI is only used for doing ad hoc experimentation on reports, whereas SSRS is what you should use if you want some standardized reporting solution.
Kindest Regards, Rod Connect with me on LinkedIn.
September 29, 2024 at 2:50 pm
Data Wrangler wrote:There are so many dead-to-me technologies, though as others have said, most live on in some form for some users.
SQL Server Reporting Services (SSRS) is dead to me. The last thing I did with it was migrate SSRS reports to Power BI as part of a data warehouse migration from on-prem to Azure a few years ago.
<snip />
We still have a lot of SSRS at work. Heck, we've got a lot of older Crystal Reports, too. But I wanted to ask you, is it hard to convert a SSRS report to Power BI? I've seen Power BI in demonstrations, but I've never used it. And some people I've worked with have given me the impression that Power BI is only used for doing ad hoc experimentation on reports, whereas SSRS is what you should use if you want some standardized reporting solution.
There are, in essence. two types of PBI reports. One type is what gets developed using PBI Desktop - and that is the graphical/analysis tool that you are referring to. But the second type of report is called a 'paginated report'. These are 95% the same as SSRS reports – the missing 5% representing the fact that there is no such thing as a PBI project and therefore no shared project-level connections.
Once I'd migrated one SSRS report, I did a before/after comparison on the RDL files – only the connection string was different. Knowing this, I migrated the others by editing the RDL files in VS Code. Piece of cake.
Editing of PBI paginated reports is performed file-by-file in Report Builder rather than VS. Functionality is essentially the same. The way in which reports are source-controlled in PBI workspaces is, however, very different from what you are used to.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 15 posts - 1 through 15 (of 27 total)
You must be logged in to reply to this topic. Login to reply