| Author |
Thread Statistics | Show CCP posts - 5 post(s) |
|
CCP Prism X
C C P
C C P Alliance
112
   |
Posted - 2011.09.22 15:07:00 -
[1] - Quote
   
Thank you, I really do appreciate that. Bookmarks like these are handy when I have half a thread raging at me for some douchebaggery of mine. 
As to the stats, I'm really not comfortable with throwing them out willy nilly. Perhaps it's something I can approach the community managers and my own superiors about releasing every now and then if there is interest. I do go over full trace snapshots every now and then, to see if anything weird is up, and send a report to my superiors. Haven't done it in a while though because the "how many things are burning" / "how much stuff do I have to do" ratio is very low at the moment.
And the DB doesn't really cry anymore (from my PoV that is. I don't consider HW or internal SQL Server faults to be the DB crying. P.S. There are no internal faults in SQL Server!).. so it might not be all that interesting. It used to cry a lot under certain circumstances when I started here as I was a 100% increase to the DB Devs here and we had also only had a single DBA. Now there's three of us (although one, belongs to CORE rather than EVE Software. But the Captain still counts as he works a whole lot for us.) and three of the DBAs. We're five years down the line from then and a lot of the legacy problems have now been ameliorated. Most of the stuff that pops up in these traces is stuff that I missed when reviewing code.
Which was, in all honesty, the best practice we ever adopted to avoid deployment issues from the DB. Rigid reviews to enforce the coding conventions and technical guardianship as soon as possible. Stuff still slides every now and then and does cause problems but I doubt you guys ever notice much of it because, all in all, there aren't oodles and noodles of already existing problems to be compounded by the newly surfaced one. Of course this is the best practice from my point of view. The DBAs down in operations have also done a great deal of work to ensure smooth deployments which used to suffer a whole lot from stats invalidating all over the cluster, query plans thus becoming very wonky and the server refusing to start up in a timely manner. And there's of course a lot of other work that has gone a long way to make my job a whole lot easier than it was. I won't pretend like it's all been in the database.. that would be blatant douchebaggery.
Now.. I'm giving 13:1 odds on the SQL Server crashing about half an hour after I post this.
~ CCP Prism X
EVE Database Developer
"Prism X is my first world problem." ~ CCP FLX
If anything in this post was informative or could be considered as 'good news' to you - chances are you've misread it. |
|
|
CCP Prism X
C C P
C C P Alliance
115
|
Posted - 2011.09.22 15:48:00 -
[2] - Quote
Alexandra Alt wrote:have you tried PostgreSQ.
I wasn't here back when these decisions were being made so I don't know if they actually made any comparisons or even looked into an alternative. The decisions, as I understand it, came down to the price of the license and the fact the MS was very keen on having a single sharded MMO to point at and say "Look, they are using our stuff and doing fine! We're totally competitive."
There are some things in TSQL that bother me.. or more appropriately there are some thing NOT in TSQL that bother me. There are some aspects of the MSSQL server internals that bother me. However, having worked exclusively in this environment for five years I'm quite certain that I'd rip out my dreadlocks if I were to switch all the sudden. That's not necessarily a bad thing as some of them are quite ratty and I'd rather be dealing with something challenging than doing gruntwork (as you can see I'd also rather post on the forums than do gruntwork) as time simply flies by when you're focused.
And there is simply no way we'd ever migrate a production DB to a new model. It's not practical, the ROI is probably negative when it comes to wasted time and lost experience/knowledge and MS have been nothing short of awesome whenever we needed them. The only thing I could complain over is that my record of keeping TQ unstable would be much higher if some MS dude wouldn't have found a very glaring newbie mistake I made in a very cowboyish way with absolutely no papertrail behind it. That was another "Eureka" moment in our DB process handling.. don't allow me to do papertrailless cowboy stuff like that again. 
~ CCP Prism X
EVE Database Developer
"Prism X is my first world problem." ~ CCP FLX
If anything in this post was informative or could be considered as 'good news' to you - chances are you've misread it. |
|
|
CCP Stillman
C C P
C C P Alliance
65
|
Posted - 2011.09.22 16:25:00 -
[3] - Quote
CCP Prism X wrote:don't allow me to do papertrailless cowboy stuff like that again.
We don't. Because we love you
Associate QA Tester for Team EVESec. |
|
|
CCP Xhagen
C C P
25
|
Posted - 2011.09.22 17:21:00 -
[4] - Quote
Contributing to Prism X's ego stroking forum thread.
CCP Xhagen | CSM Project Manager |
|
|
CCP Wrangler
33
|
Posted - 2011.09.22 20:49:00 -
[5] - Quote
Zagam wrote:CCP Xhagen wrote:Contributing to Prism X's ego stroking forum thread. Y'all are going to have to get new doors, so PrismX can go home today.... unless you lock him in the server room or something... (that said, I have to admit I enjoy seeing all of the devs posting, and showing a sense of humor) Locking up Prism X doesn't work, he somehow manages to get out no matter what.
Wrangler
Community Team Manager - Community Arch Wizard
Although personally I am quite content with existing explosives, I feel we must not stand in the path of improvement. - Winston Churchill |
|
| |
|