sqlcook

5 ms·

1.
by sqlcook 5mo ago
Sad news, I’ve worked at HumanLongevity and got to interact with Craig several times. He was a legend and truly will be missed.
2.
by sqlcook 2y ago
You’re missing the point of the benefits of solutions like these, and the original set of tools like the Informatica of the kind. Those tools come with limitations and constrains, like a box of legos you can build a very powerful pipeline w
3.
by sqlcook 6y ago
This is indeed one of the nicest UI's I've seen, is this all custom made or are you using some open components? I wanted to get similar effect for something completely different I had in mind (like a flow based diagram), any advic
4.
by sqlcook 8y ago
Nice if you’re only connecting to a single instance, nightmare if you have multiple. DbVisualizer is better imho.
5.
by sqlcook 8y ago
It actually IS quite hard to imagine solid engineers finding it hard to learn simple SQL. It's a lot harder to write "nasty" sql than "nasty" js, and if you're a front-end dev struggling with sql, then you prob
6.
by sqlcook 8y ago
EE features without support. I hate to bring up Mongo as example, but something similar...where support, additional software/plugins and cloud hosting are where the $ is made. I did thorough testing of Memsql two years ago but went wit
7.
by sqlcook 8y ago
Hi Rick, I've been following Memsql for a few years now, are there any plans to release "community" edition? Last time I checked about 1.5 years ago json support was very basic and EE pricing (dont remember exact #s) was rath
8.
by sqlcook 9y ago
You mean with a picture of your face....
9.
by sqlcook 9y ago
Nice looking app! What did you use for the charts?
10.
The Sixense Sense was once the ultimate VR controller. Where is it now?(theverge.com)
1 points by sqlcook 9y ago|0 comments
11.
by sqlcook 10y ago
Excellent work Slava! Have been planning to migrate to RethinkDB for one of the existing projects, great timing with Horizon :D
12.
by sqlcook 10y ago
if you want the fastest ingress, disable replica until your ingress is done, its faster to create replica at the end of ETL for that given index. Also, you want to disable auto allocation as well, this will disable shard movement during ing
13.
by sqlcook 10y ago
100 data nodes basically if you want fast ingress, keep shards small, once they get past ~5-10gb , ingress significantly slows down. Also this was on ES 1.5 , have not tested latest 2.0+ builds
14.
by sqlcook 10y ago
I've indexed ~ 1 million docs a second, but with proper routing, can probably even 5x that. Total cluster size was 50 terabytes, at the end.
15.
by sqlcook 11y ago
The post is about Postgres, you were referring to MSSQL mirroring, which can fail back from primary to secondary and back to primary almost seamlessly, depending on type of failure and log catchup. Postgres has been a pain as described in t
16.
by sqlcook 11y ago
? MSSQL mirroring failover is very easy and painless( arguably one of best compared to other rdbms), just make sure not to do automatic failover as that can cause false failover with spotty network between nodes and witness.