Last week I was frustrated because the SATA-to-USB converter my co-worker gave to me suddenly stopped being recognized by my laptop.
and I still have to remind myself of this from time to time. I've been in IT longer than you've been alive. In IT, if it's not powering on, it's far more likely it's a boring problem like the switch on the power strip is off than it is something sexy like a fried motherboard. In fact, the medical industry has a saying: "When you hear hoofbeats, think horses, not zebras." Meaning, look for the common causes first before jumping to exotic maladies. Can you help me to understand what the network transfer rates have to do with memory usage on the actual server?" It's good to know you've installed things to CAT6 spec. That is, pretend you're just an inexperienced kid and use their hubris against them. In the case of SQL Server, be able to cite Microsoft's own recommendations for SQL Server memory allocation. But, yeah, some people are assholes that simply cannot fathom someone barely out of high school could possibly know anything useful.ĭon't let the bastards grind you down. Some of it has less to do with your actual age and more to do with others trying to find out exactly how much you know.
#K.i.s.s. keep it simple stupid professional
An IT professional should not go mucking about in random systems without legal protections in place. I don't care if the person you're helping is your mother. That implies a business, which means you don't touch it without a) being a direct W2 employee, or b) having a signed contract in place. Causing someone to skip "Is the computer plugged in?" straight to "The motherboard is fried." It seems best to start at the simplest solution and moving up.įirst: Be wary of "helping someone" with their production box. Maybe i'm wrong but I feel like the longer you are in IT (or anything else for that matter) you tend to skip past the baby steps. That's awesome, but that's not the problem here. This was after having a call with third party IT who jabbed at my lack of experience and knowledge and how his network is "cat 6 certified". I checked and SQL was using 76% of the RAM (out of a total 89% in use).
To only give SQL the remaining 1GB? It's no wonder the thing is slow. To keep a safe margin in hardware I always figure the OS is using ~4GBs alone.
#K.i.s.s. keep it simple stupid windows
First thing I see is the server is running Windows 2012 and SQL with only 5GBs of RAM! That's just crazy. Checking things like CPU and RAM seems like a go-to move. So to help this person out I remoted into their server and checked the usual areas.
Not something I really enjoy but it's understandable. I am on the younger side of IT (19 and counting) so it isn't uncommon for my knowledge to be brought into question. I've been helping someone with server performance issues, and specifically and application that uses SQL as the main database. Half of this is for venting purposes, the other out of curiosity.
0 kommentar(er)
