Re: "Cult of the Wintel PC" raises head at AWC's switch to Macs

Jim wrote:
In article <e17d099f-0a2f-4984-a524-decab862e789@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
ed <news@xxxxxxxxxxxxxxx> wrote:

On Mar 7, 5:51 pm, Jim <j...@xxxxxxxxxxxxx> wrote:
In article
<1c4338c5-6f6e-4623-bca0-3b554d544...@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
<snip>
Not accordint to M$ as I read it.

"A SQL Server CAL is required for a device (for example, a personal
computer, workstation, terminal, personal digital assistant, or mobile
phone) to access or use the services or functionality of either edition
of SQL Server."

Which is what AWC appears to be claiming as well.
jim, are you f'in' kidding me- how do you think that contradicts what
i've been saying the whole time?- if you keep the server ms, it
doesn't matter what the client is- you've still got to pay for a
client license. from my very first post, i said "you can switch the
backend stuff, and rewrite your client software in java, and not have
to switch to costlier hardware."

and second
moving to xServes when the current hardware the SQL is running on is
changed out. Then they have no licensing fees to pay over what ever life
cycle (read years here) is for them.
THIS part is correct, and is consistent with what i've been saying all
along- changing the server software removes the need for the
licenses. but ms sql is the ONE piece that they say they are
KEEPING. you REALLY didn't read the article very well, did you?
I went to M$ page on SQL server along with reading the article. M$ does
like money, a lot of it.

There are other M$ server costs as well,

" AWC has also finished migrating from Microsoft's Active Directory to
Apple's Open Directory for controlling the network. This is especially
significant, Frantz says, because the controlling operating system
architecture determines licensing costs.
yes jim, that's what i've said the whole time. what the server is
running- that's the "controlling operating system architecture" in
that quote- determines what your client connecting licensing costs are
going to be, not the client itself.

"By getting off of Microsoft Active Directory and onto Open Directory,
each individual server becomes separate and Microsoft can no longer view
[and charge for] a broad enterprise network. This was a very significant
change," Frantz says. "

Did you read the article?
yes i did, and all your quotes SUPPORT what i've been saying, and what
you've been arguing against! it's become very clear you have no idea
what the article actually means!

holy crap jim, you are seriously dumb. i didn't claim to be any kind
of expert, i didn't insinuate it, and i didn't imply it. it was
brought up, in context, to show that i obviously don't have a hate of
apple/macs as you imagine i do.
I didn't say you hate of Apple/Macs at all.
no, that was a bit of hyperbole (but not much)- you did say i DISLIKE
apple/macs, which is also very much not true.
You just love M$ more,
that's all and are one of their cultists.
no jim, you only think that because YOU are an apple cultist, and a ms
hater, as evidenced by you using 'm$' :P . i simply think they're
both companies out to make a buck, neither one is any better than the
other, and their products both have their pluses and minuses.
I'm a Mac "cultist" though I have Macs, Windows and a Solaris box and
recommend the task-driven solution for my clients not a Mac Centeric one
which only goes to show that you don't know squat about what I recommend
for what situation.

The task defines the software and together they define the hardware. If
it runs on all hardware, then you have other factors to look at.

All in all, at least in this case, I'm sure the article didn't enumerate
all the costs so we don't quite know what's going into that $1.82M
savings. For one, they spoke of a 3 year hardware cycle. Macs in
schools, where they typically get beat on worse than in a corporation,
have a mostly 5 year life cycle with KB,M or HD repairs so they may save
money there with a lengthened hardware cycle for one.
dude, companies don't typically run 3 year cycles because the things
wear out and need to be replaced.

Frantz said that was their cycle. Do you doubt what he said? You must since I still get the impression you know or act as if you know their set up better than what they said in the article(s)

We can stop at that.

<snip>

3 years seems normal in my experience, with some 4 or 5 years. You typically have the equipment under vendor maintenance during that period so one is not concerned with things "wearing out and needing to be replaced".

Steve
.

Relevant Pages

  • Re: Web Server Setup
    ... Also, have a bunch of space for temporary SQL dbs, just for playing and tests. ... the specifications you described might be just the hardware for the test machine. ... I need to set up a server to handle an application that will pretty much ... 146GB Drives w/ RAID and dual hot swappable power supplys. ...
    (microsoft.public.windows.server.general)
  • Re: MSCS Questions
    ... hardware won't necessarily speed things up. ... > server solution than we had, including more memory and faster processors. ... > I understand that clustering isn't a performance benefit, ... >> Andrew J. Kelly SQL MVP ...
    (microsoft.public.sqlserver.server)
  • RE: Fulltext failure on a 2 node cluster
    ... Server full-text search resource online: "SQL Cluster Resource 'Full Text' ...
    (microsoft.public.sqlserver.clustering)
  • Re: HELP PLEASE ~ ???
    ... You mentioned that it went ahead and added a SQL ... SQL Server 2000 database for all my data. ... find the connectionString in the newly recreated SQLExpress database. ... The connection string specifies a local Sql Server Express instance ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Multi-Channel Raid VS SAN Storage
    ... A 5~6 years old server is a very old server. ... As I mentioned, the server is one node in a cluster environment, and SQL is ... We actually are running RAID 1+0 and our aplication is definately more ... needs it's own SAN device, or at least a dedicated IO channel on the SAN. ...
    (microsoft.public.sqlserver.setup)