Viewing 9 posts - 1 through 9 (of 9 total)
The IOPs calculation for the disk needs further explanation, there are a lot more factors involved in how many IOps you can get out of a physical disk, for example...
May 1, 2012 at 2:13 am
Personally I think most tables should have a surrogate key, there are exceptions, but the rule is have one imho.
Why? As I detail in my blog article - this is...
October 25, 2010 at 2:10 am
I wrote a blog article a while back on the theory on surrogate keys based around Codd and Date.
The link: http://sqlblogcasts.com/blogs/tonyrogerson/archive/2010/03/13/database-design-surrogate-keys-part-1-of-many-rules-for-surrogate-keys-e-f-codd-and-c-j-date-research-and-problems-they-solve.aspx
Reminds me - I need to go back and finish...
October 25, 2010 at 1:04 am
I wasn't going to respond because I knew I'd get grief for taking the opposite view to you Paul and Jeff and no doubt a few others that are proponents...
September 2, 2010 at 11:09 pm
Jeff - there is absolutely no need to take that tone with Hugo.
Hugo is correctly, I have also pointed out the foolishness of relying on this method, a method that...
September 2, 2010 at 10:28 pm
Putting implementation issues aside, its good practice to use surrogate keys because there is then one copy of the real data - you aren't duplicating it (as the foreign key...
May 26, 2010 at 12:09 am
I fleet about a bit - so little time; spare time is going on research around my MSc in BI which is seeing me reading way too much around the...
May 26, 2010 at 12:04 am
I have seen lot of tables with IDENTITY column created with PRIMARY KEY. I am sure we shouldn't create Clustered index/primary key on an IDENTITY column. This is not a...
May 25, 2010 at 10:10 am
In the Relational Model (the context I was speaking in because we are on a SQL Server forum and its SQL we are talking about) sets have no order.
February 23, 2010 at 12:50 pm