Gotta love that MongoDB

MS SQL Server 2017 on Linux Has Released FTFY

@fuznutz04 said in MySQL configuration best practices: @emad-r What is your practice for log rotation? For example, the error log. If that grows (obviously indicating other issues) , and needs to be rotated, what procedure do you use to rotate logs? Currently the third party vendor uses this: expire_logs_days = 10 max_binlog_size = 100M In our MySQL instance.

We have plans to add an in memory database to ML in the future when more performance is needed, as well.

Oh that's funny and interesting! Might I ask what sort of work so I can see a little bit about what is done?

@matteo-nunziati said in Pronunciations of SQL Derived Database Names and Terms: we have a company in my town: second quadrant. the provide professional postgresql support worldwide and they pronunce it "postgres". omitting the final "ql" That's the official pronunciation and it was originally spelled that way. The PostgreSQL spelling was added when it went open source.

@scottalanmiller said in Why Does Everyone Still Focus on Relational Databases?: I just built out a NoSQL ElasticSearch three node cluster in the lab. Whoo! The perfect DB setup for storing a hit counter for the number of times I've watched Tombstone!

They work very differently too. MySQL's features vary significantly based on which engine is in use. They perform differently, have different relational abilities, store differently on disk (MyISAM is one file per table, InnoDB is one file for everything) and use different tools.

@alvama said: Scott, thank you for your topic. I am planning new installation and comparing between RAID 10 and RAID 5 on ssd drives. What do you think about stripe size and TBW for two types of raid? Do you know what size of blocks will be written on disks if service (sql for example) writes 8Kb on volume. For raid10 I think it will be two 8K blocks on mirror disks. But for RAID 5 it will be two blocks with size=stripe size and may be 32 or 64K. And in raid5 configuration TBW limit will be reached faster. I'm not Scott but in your context RAID5 seems to be preferred. Because 1) Flash and not spinning disk used so typical parity RAID issues associated with high-capacity spinners are gone (see URL below) 2) Database logs are sequential writes of a big sizes so should "touch" maximum amount of spinners possible and because of sequential nature read-modify-write is not going to happen and 3) RAID5 gives you write performance of (N-1) and RAID10 does (N/2) (where N = amount of spinners). https://slog.starwindsoftware.com/raid-5-was-great-until-high-capacity-hdds-came-into-play-but-ssds-restored-its-former-glory/ Good luck

@JaredBusch said: What the hell is up with the author of that article basically down playing the entire thing because it does not prevent SQL injection? Seriously WTF? I agree, that is a bunch of BS. This is about on-disk data at rest security and is a decently big deal.

Good read, thanks.

A year later and no one posts. Just came across this today. Did not realize that Rackspace has added a Redis and MongoDB product! http://objectrocket.com/