Been there. Server, Server2, yada, yada. Replaced them all and made that go
away, as fast as possible. :)
I suppose you could always do the air quotes thing, and ask, is that server or
"server"?
Seems like a name change would be in order but as I recall SQL doesn't really
like that all that much, at least not without lots of gyrations, and if they
store things with UNC paths it can be propagated in the data as well.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of geoff
Sent: Monday, July 14, 2014 2:33 PM
To: [email protected]; '[email protected]'
Subject: RE: [NTSysADM] Stupid terminology question
But the client calls their SQL instance "server", hence the confusion. I need
to distinguish.
I'm just Playbookin' around
________________________________
From: "Senter, John" <[email protected]<mailto:[email protected]>>
To: "'[email protected]'"
<[email protected]<mailto:[email protected]>>
Sent: 14 July, 2014 2:12 PM
Subject: RE: [NTSysADM] Stupid terminology question
+1 on server
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Tony Patton
Sent: Monday, July 14, 2014 2:00 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [NTSysADM] Stupid terminology question
Server?
T
On 14 Jul 2014 18:51, "geoff"
<[email protected]<mailto:[email protected]>> wrote:
OK sanity check please.
When referring to the system your windows O/S tied to whether it is physical or
virtual what term do you use? Essentially I need a good term that covers both
physical and virtual in a single term.
The best I have come up with is host but even that is confusing in some circles.
Rant below if you want to read it
<steps up on soapbox>
I have numerous clients that refer to their server by their application name.
OK, I get that. They see their environment as important, and don't care about
the underlying O/S. But when I report some problem to them that involves the
hostname they are like the proverbial deer in the headlights. "But that's not
what it is called!" they retort. In the old days I would bite my tongue and
patiently explain that my hostname is the physical system supporting their
environment and with faces sufficiently saved we would move on. Now I get "But
there isn't this a virtual server?"
Hence my question.
Don't even think about the discussion that ensues when it is getting underlying
ESXi server that has an issue.
<soap box stowed beneath desk till next needed>
gt
I'm just Playbookin' around
