PowerPivot Expo – Tomorrow
At one of the largest Business Intelligence-focused virtual events of the summer, SSWUG.ORG is hosting eight sessions on PowerPivot! Learn from experts such as Mark Tabladillo, Brian Knight, Jen Underwood and others about organizing, connecting and manipulating tables of large data sets.
If you want to attend, you should! After all, it’s free to attend the "Best of SSWUG.ORG" track and a minimal fee to access the "Premium" track.
All-In-One and One for All
Today I was reading an article about the benefits of All-In-One computer systems for the corporate environment. The article stressed that the machines were used for software development, and had plenty of horsepower.
The key point made was that the machines were more portable, easier to deploy, and if bought in higher quantities, could share a base image when configuring a new workstation, or re-configuring an existing one with a problem or for a new user.
The article stressed that this capability reduced the total cost of ownership.
I’m finding it hard to believe that using an All-In-One computer reduces the cost of ownership unless it reduces power consumption or something like that. It seems to me that the real reduction in cost is the standardization of hardware reducing support costs.
One reason I am confused is that the article stressed that even though these computers come in a single package, there are many options you may purchase. Well, there goes the standardization of a machine to a certain degree.
What has been your experience? Is the standardization worth the effort? Are you able to purchase enough machines at a time to get similar hardware? Where do you find your cost savings?
Reader Comments
Composition vs. Inheritance
Jeffrey writes:
I was taught, long ago, that inheritance should go from the general to specific. From Vehicle to Car to RaceCar to BRM.
The argument is easier for those of us who have built something real.
Thanks for your excellent examination of the controversy.
Your comments are valued when you send them to btaylor@sswug.org.
Cheers,
Ben
$$SWYNK$$
Featured Article(s)
The Procedural DBA (Part 3)
The predominant reason for using SCOs is to promote code reusability. Instead of replicating code on multiple servers or within multiple application programs, SCOs enable code to reside in a single place: the database server.
Featured White Paper(s)
Query Tuning Strategies for Microsoft SQL Server
Written by Quest Software
When you’re looking for a reliable tool to diagnose … (read more)
Featured Script
dba3_SimpleHistoryTable_Trigger_demo
demonstrates general approaches on how to construct and query a history table… (read more)