Automatic Updates
Yesterday, as I was writing about Continuous Release, I was trying to think of examples that would be common to you. One I suggested would be the Google Chrome Browser. You may well have known that. But, did you know that Adobe Flash, as encapsulated in the Google Chrome Browser, automatically uploads the latest release to your computer when using Chrome? In fact, add-ins for Google Chrome often have continuous release built in.
Windows Updates is a Continuous Release feature we experience in the Microsoft world. By default, it is turned on, to automatically downloads and updates software patches to your computer. The patches may be for the operating system, client software, or even services such as IIS, SQL Server, etc. Because the default configuration is automatic download and install I am equating it to continuous release.
I don’t seem to have much problem with Chrome as a result of continuous release, and even if I did, I can fall back on other browsers for support. But what about Windows Updates? Are they ok to be automated, and if so, in what environments?
Have you ever had your computer restart in the middle of doing something because it had applied updates requiring a reboot? If Chrome did that I would have un-installed it long ago.
Have you experienced down time on a server due to Windows Updates? Do you test them in another environment before applying them to your production machines? Should an Accidental DBA rely on Windows Updates or apply updates manually? Do you get tired of the nagging built into Windows reminding you if you don’t have automatic updates turned on?
Share your thoughts on Automatic Updates, or, the Microsoft Continuous Release process, by writing btaylor@sswug.org. Lets find out if there is some common experience and even guidance for others with workstations, laptops, tablets or Servers.
Cheers,
Ben
$$SWYNK$$
SSWUGtv – Close the Interview
With Stephen Wynkoop
How do you successfully close an interview? Find out, with Laura Rose’s professional development tips.
Watch the Show
Featured Article(s)
Column-Level Security with Views
Perhaps using views is the best option when it comes to restricting access to a certain column or columns within a table. First, you create a view that selects all the columns from the underlying table except those ones you want to make inaccessible. Then, you grant the SELECT privilege on that view to your users, rather than granting this privilege on the underlying table.
Featured White Paper(s)
Achieve an astounding return on investment with Toad® for Oracle
read more)
Featured Script
Person’s Current Age, Birth date to Age
Using a birthdate, determine the correct age of a person… (read more)