DBAs, man
-
@JaredBusch Believe me or not. He wanted smaller SSDs for a SAN because #reasons, and this was his primary concern.
This is why a DBA should never even know what is behind the scenes. He's trying to be the server tech behind the system admin!
-
@scottalanmiller said in DBAs, man:
@JaredBusch Believe me or not. He wanted smaller SSDs for a SAN because #reasons, and this was his primary concern.
This is why a DBA should never even know what is behind the scenes. He's trying to be the server tech behind the system admin!
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
-
@scottalanmiller said in DBAs, man:
@JaredBusch Believe me or not. He wanted smaller SSDs for a SAN because #reasons, and this was his primary concern.
This is why a DBA should never even know what is behind the scenes. He's trying to be the server tech behind the system admin!
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
WHO told you wouldn't work well in a VM?
-
@scottalanmiller said in DBAs, man:
@scottalanmiller said in DBAs, man:
@JaredBusch Believe me or not. He wanted smaller SSDs for a SAN because #reasons, and this was his primary concern.
This is why a DBA should never even know what is behind the scenes. He's trying to be the server tech behind the system admin!
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
WHO told you wouldn't work well in a VM?
The vendor, of course, lol. We promptly ignored them.
-
@scottalanmiller said in DBAs, man:
@scottalanmiller said in DBAs, man:
@JaredBusch Believe me or not. He wanted smaller SSDs for a SAN because #reasons, and this was his primary concern.
This is why a DBA should never even know what is behind the scenes. He's trying to be the server tech behind the system admin!
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
WHO told you wouldn't work well in a VM?
The vendor, of course, lol. We promptly ignored them.
I'll never understand the willingness to pay a vendor to be your vendor who doesn't even have a passing knowledge of their own product!
-
@scottalanmiller said in DBAs, man:
@scottalanmiller said in DBAs, man:
@scottalanmiller said in DBAs, man:
@JaredBusch Believe me or not. He wanted smaller SSDs for a SAN because #reasons, and this was his primary concern.
This is why a DBA should never even know what is behind the scenes. He's trying to be the server tech behind the system admin!
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
WHO told you wouldn't work well in a VM?
The vendor, of course, lol. We promptly ignored them.
I'll never understand the willingness to pay a vendor to be your vendor who doesn't even have a passing knowledge of their own product!
*shrug* This is one of those things where a product was purchased and IT was told to make it happen. So we did. Somebody had a sign hung on their door that became our unofficial motto... it's a quote I've seen attributed most often to Mother Theresa.
"We've been tasked for so long to do so much with so little that we are now finally qualified to do anything with nothing."
Our few drops of so little let us shift from nearly 30 physical servers at our largest point down to 4 systems from Scale computing when I left. (They have since upgraded and are now running six nodes, IIRC).
We also went from having physically separate switches for our different networks to ~50 various model HP Procurve switches as well.
-
@scottalanmiller said in DBAs, man:
@scottalanmiller said in DBAs, man:
@scottalanmiller said in DBAs, man:
@JaredBusch Believe me or not. He wanted smaller SSDs for a SAN because #reasons, and this was his primary concern.
This is why a DBA should never even know what is behind the scenes. He's trying to be the server tech behind the system admin!
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
WHO told you wouldn't work well in a VM?
The vendor, of course, lol. We promptly ignored them.
I'll never understand the willingness to pay a vendor to be your vendor who doesn't even have a passing knowledge of their own product!
If that's the case, then how you can buy nearly anything - that seems to be the general theme with all sales people.
-
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
WHO told you wouldn't work well in a VM?
The vendor, of course, lol. We promptly ignored them.
Several of our clients use the same LoB software (it's the "defacto" for this industry) and this vendor keeps telling us that the data cannot be stored on a RAID setup nor virtualized. Whenever there is an issue with their software, they always blame RAID -- even though the backend is MS SQL.
-
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
WHO told you wouldn't work well in a VM?
The vendor, of course, lol. We promptly ignored them.
Several of our clients use the same LoB software (it's the "defacto" for this industry) and this vendor keeps telling us that the data cannot be stored on a RAID setup nor virtualized. Whenever there is an issue with their software, they always blame RAID -- even though the backend is MS SQL.
WOW - what the hell do they expect you to run it on? JBOD? single drive?
-
@Dashrender said in DBAs, man:
Yepp. At my last job, we had our SQL Server virtualized. It ran link a champ for some stuff that we were told wouldn't work well in a VM.
WHO told you wouldn't work well in a VM?
The vendor, of course, lol. We promptly ignored them.
Several of our clients use the same LoB software (it's the "defacto" for this industry) and this vendor keeps telling us that the data cannot be stored on a RAID setup nor virtualized. Whenever there is an issue with their software, they always blame RAID -- even though the backend is MS SQL.
WOW - what the hell do they expect you to run it on? JBOD? single drive?
Those would be the options
-
@Dashrender : Bare metal, single drive, no AV is their recommendation. Because, ya know, it's still 1995...
-
@Dashrender : Bare metal, single drive, no AV is their recommendation. Because, ya know, it's still 1995...
What industry so readily thinks that that is okay and doesn't demand production level systems?
Even in 1995, that wasn't an okay design.
-
@scottalanmiller DBAs. There is still a prevalence of thought that they must have lots of separate drives for any number of purposes. These 'drives' all go to the same two or three luns, and some drives are in the same datastore, so.... splitting drives is just splitting hairs. It makes it easier to see database size, though a good DBA should be able to manage that without complication.
