1.
Database Science: SAAS Multi-tenant Databases Jul 23, 2008 ... Given enough tenants in a database, adding a tenantId to a mutli-tenant database is recommended as some queries are going to be at least an ...
2.
Database Science: Is SQL Slow? Feb 25, 2009 ... Is SQL Slow? Last time I demonstrated a case where stored procedures are ... Deciding where to execute code, in the database or elsewhere, ...
3.
Database Science: Can a timestamp be slower than a datetime? I generally advise development teams to avoid the timestamp datatype in MySQL for business data such as a purchase date since the datetime datatype is much ...
4.
Database Science: Can a timestamp be slower than a datetime? For example, for this simple sql, when purchaseDate was a timestamp, the query took about 9.4 seconds and the datetime version took about 4.3 seconds. ...
5.
Database Science: Can a timestamp be slower than a datetime? I generally advise development teams to avoid the timestamp datatype in MySQL for business data such as a purchase date since the datetime datatype is much ...
6.
Database Science: Can a timestamp be slower than a datetime? For example, for this simple sql, when purchaseDate was a timestamp, the query took about 9.4 seconds and the datetime version took about 4.3 seconds. ...
7.
Database Science: Implementing Sharding in the Database Jan 21, 2009 ... This might sound a bit like an advertisement for the MPP version of DB2, but if it were open source I would at strongly consider ...
8.
Database Science: Joins are slow, memory is fast Both one month of the sale table and the product table both can’t fit into memory; instead of fast memory access we are dealing with slow disk reads and ...
9.
Database Science: Clustered indexing and query performance Feb 22, 2008 ... This time I’m going to show a way to get better performance by selecting a good clustered index. With the InnoDB, the create table primary ...
10.
Database Science Some may find it surprising that it take less time to ship 1 million rows out of the database and then summarize it in code than it does for MySQL to ...
|