If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...

If you have a not-so-usual solution for your problems but need to justify it to your boss...

If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...

...then 'No Bugs' Hare on Soft.ware might be the right place for you.

Your mileage may vary. Batteries not included

Assorted Rants Tagged ‘SQL’, page 1:

OLTP Database Optimization 102 – DIY Heterogeneous Replication (Part II)

posted October 31, 2017 by "No Bugs" Hare

Quote:	“The point of Super-Replica is that it is a replica Slave DB which is larger than original Master DB”
Another Quote:	“this “don’t write some HISTORICAL data to Master DB” approach can easily allow to reduce the load on the Master OLTP DB by a factor of 2x-3x”
	[→]

posted October 24, 2017 by "No Bugs" Hare

Quote:	“there are still several Big Fat Reasons™ to use DIY replicas”
Another Quote:	“With the Replication Messages described above, it is ok to apply Replication Messages to Slave DB which is newer than exactly necessary.”
	[→]

posted September 5, 2017 by "No Bugs" Hare

Quote:	“Have I already mentioned that you DO need to understand execution plans?”
Another Quote:	“DO keep in mind that maintaining indexes has its own cost”
	[→]

posted August 29, 2017 by "No Bugs" Hare

Quote:	“If I was a compiler-with-ability-to-create-indexes-as-I-need-it – what would I do to make The Ideal Execution Plan™ for this request?”
Another Quote:	“When we have that ideal-execution-plan – we still need to convince our SQL compiler to use it”
	[→]

posted August 24, 2017 by Ben Richardson

Quote:	“A correlated sub-query is a type of query, where inner query depends upon the outcome of the outer query in order to perform its execution.”
Another Quote:	“Correlated sub-queries are slower.”
	[→]

posted August 22, 2017 by "No Bugs" Hare

Quote:	“to realize how our queries are working – we need to start thinking in terms of so-called “execution plans”.”
Another Quote:	“it can be faster to use Table Scan rather than Index-Scan+fetch over such a low-selectivity index”
	[→]

posted December 5, 2016 by "No Bugs" Hare

Quote:	“while duplication MAY indeed improve performance – undue duplication also MAY hit performance pretty badly”
Another Quote:	“NoSQL will usually call for another denormalisation on top of what we’ve described above for SQL-with-XML.”
	[→]