This had been a busy week for updates. I finished adding new builds to build lists for 2017, 2016, and 2014, the first time I’ve done these platforms on the same day. To be fair, two updates were on a 19th and on the 20th, but that’s pretty next to the same day. In past times I’ve had updates diverse versions during different months.
It doesn’t be the case into the future. SQL Server 2017 is around the CU model where we all monthly updates towards the product. No more service packs to do this version. Any time you hadn’t heard that, there will be the new servicing model that consist of just the monthly updates. I wasn’t positive that I liked this in the early stages, but I do appreciate that people don’t get wrongly identified as trying to decide which CU1 is needed choices were different patches for RTM, SP1, SP2, etc. Now I’ve gotten would always expecting an update each and applying them after several days. Until now, Microsoft has mostly been sticking to monthly releases, nevertheless the December release got delayed into January. With holidays, that’s expected.
Yesterday also saw the update of SSMS to v 17.6. You could potentially freely make use version and download total install merely the update package in case you’re running 17.x. We are seeing updates within the fairly consistent basis to the tool, every couple of months. I hope we will continue to increase see more fixes and enhancements aside from new functionality as SSMS was neglected for several days. I don’t know how stable this version is, but 17.4 was modest machines for years without an evil results, and I think this seems for now.
Updates were always a part of software, but they are often fairly rare, with interruptions occurring just a few times 1 yr. That’s changing. Redgate releases software each and every week, with in relation to product updating once or twice a month. For that uses relatively few fecal material software, all of a sudden it appears as if I have a regular set of tools to update across my SQL Server development platform between SQL Server, SSMS, VS, Redgate tools and.
That’s good, site i found loads get fixes and increased functionality, but across male tools, I might find myself updating something day to day. While the software often updates itself plainly click OK, I’ve got to make a decision as well as process is disruptive and frustrating, especially when I make required updates, which happens much more than I’d like. I really like the idea of DevOps, only one of the unintended consequences is actually everyone need to, there are a lot of changes and updates for users to handle.
I don’t have an answer, but I do find myself delaying updates a growing number of, often moving merely take every 3 or 4 updates. Maybe if everyone had a straightforward to apply patches with PoSh across systems, or smoother built-in mechanisms I’d feel differently, for now I probably click “skip” more “apply”.