192 reputation
111
bio website syneticon.net
location Germany
age
visits member for 2 years, 3 months
seen Apr 14 at 8:55

I am working for a company which is doing infrastructure operations and IT consulting jobs in Germany, Europe.

My sphere of activities includes virtualization topics, IP networking, storage, server operations, monitoring, backups and network security. I was awarded the Microsoft MVP title for Windows Networking for several years in the past, although my public activity on Microsoft-specific topics has declined seriously due to lack of time so it is not likely to happen again that soon.

If you need to get in touch, just mail the company: office@syneticon.net

If you are wondering about the avatar bunny, Ubisoft supplies a lot more to look at and wonder about.


Feb
18
awarded  Popular Question
Sep
19
comment MySQL hogging memory
@AleksandarIvanisevic Nope, I still can see the effect with the pre-current GA release 5.6.12. Apparently, the issue only arises with complex queries using multiple tables.
Sep
17
comment SQL Server 2012 x64 - cannot safely allocate more than 50% RAM
@TomTom as it seems to take the OS down with it, it probably is not.
Apr
29
awarded  Commentator
Apr
26
awarded  Citizen Patrol
Apr
26
awarded  Promoter
Apr
26
awarded  Tumbleweed
Apr
24
comment MySQL: logging queries which would execute without using indexes
After pondering around with pt-query-digest I found it extremely useful for exactly the reasons you've cited. Thanks for that.
Apr
24
accepted MySQL: logging queries which would execute without using indexes
Apr
22
comment .mdf vs .ldf Performance considerations
Performance characteristics put aside, it might be a good idea to put logs on HDDs as long as the long-term reliability of heavily-written SSDs is still unclear. HDDs have served well as log devices for decades now, their deficiencies are well understood and can be planned for.
Apr
20
revised MySQL hogging memory
added 56 characters in body
Apr
20
revised MySQL hogging memory
added 830 characters in body
Apr
19
revised MySQL hogging memory
added 148 characters in body
Apr
19
revised MySQL hogging memory
added 681 characters in body
Apr
19
revised MySQL hogging memory
added 365 characters in body
Apr
19
revised MySQL hogging memory
added 1699 characters in body
Apr
19
revised MySQL hogging memory
added 35 characters in body
Apr
19
asked MySQL hogging memory
Apr
19
comment MySQL: logging queries which would execute without using indexes
Thank you for your time. I basically wanted to only have queries listed for tables where I actually might consider adding an index. MySQL's behavior is rather counterintuitive in this respect as it even would log stuff where indexes cannot be added any more (because they are there already). But I guess I could use min_examined_row_limit as a workaround.
Apr
18
accepted MySQL: replicating to a different table engine type