Viewing 15 posts - 661 through 675 (of 1,353 total)
We need to be careful that we don't underestimate the difficulty simply because we are good at it, and presumably comes more naturally to us. I used to think...
April 17, 2015 at 12:48 pm
Any ideas how this might work in an OLAP environment? At least in my world, this is where this situation is more likely encountered.
April 15, 2015 at 1:16 pm
but by avoiding key lookups, or worse table/index scans
assuming the table is not a heap (which it shouldn't be, right?), why would it (at least as a general rule) not...
April 10, 2015 at 9:10 am
If I can add two include columns to an index and get a query that runs 10 times a second down from 400ms to 10ms, you bet I'm going to...
April 10, 2015 at 9:05 am
Interesting. I haven't personally made much use of include indexes since they do make the indexes bigger and I'm not convinced the performance gains are significant. I know...
April 10, 2015 at 8:24 am
As a general rule, isn't the first one more suited to
SELECT ROLE_ID
WHERE PERSON_ID = ?
while the second is more suited to
SELECT *
WHERE PERSON_ID = ? AND ROLE_ID = ?
In...
April 10, 2015 at 8:14 am
in the real world this typically ends up being a type 1, 2, or 3 slowly changing insert / update
How does it end up being a type 3? If...
April 7, 2015 at 2:18 pm
There's a lot of things that can happen, but these are all fringe examples, at least in the current political environment. You can't guard against everything, and if you...
April 6, 2015 at 1:52 pm
To add one more of the same opinion: triggers have a place, usually for data auditing. I've also used them to enforce a low-level type of referential integrity that...
March 27, 2015 at 9:39 am
I wouldn't be too concerned about using something like SKU and OrderDate as part of a clustered key, even the key itself is wide, because it's something that probably needs...
March 27, 2015 at 7:37 am
btw. natural keys will make the index wider than an integer. I would prefer to see a database properly normalised and applications properly thought through, but then again the real...
March 27, 2015 at 6:55 am
If the database fits in memory and the load is adequate, where locks and page splitting is not an issue, then GUIDs is not necessarily a practical problem, just a...
March 26, 2015 at 9:54 am
Add a column to the child table with the proportion broken. One line would have 0.6 and another 0.4 for example. The total is multiplied by these amounts....
March 24, 2015 at 2:27 pm
A column to identify the portion of the overall value would seem to work. Not enough information presented to be sure that's the ideal solution.
March 24, 2015 at 1:24 pm
For that reason, a sequential integer will generally prove more efficient than a GUID.
Why did you qualify this? Wouldn't this always be true? That doesn't mean that there's...
March 24, 2015 at 11:14 am
Viewing 15 posts - 661 through 675 (of 1,353 total)