Viewing 15 posts - 136 through 150 (of 432 total)
Revenant (3/21/2011)
David Portas (3/21/2011)
March 21, 2011 at 2:15 pm
Revenant (3/21/2011)
March 21, 2011 at 11:37 am
Steve Jones - SSC Editor (3/21/2011)
I'd argue that SQL needs a replacement, or that RDBMSes are fundamentally flawed.
A DBMS based on SQL is not an RDBMS. It is SQL, not...
March 21, 2011 at 9:57 am
Eric M Russell (3/21/2011)
Aging and inadequate are not descriptive enough terms; could you elaborate more on what you perceive as the "fundamental problems of SQL"?
The problems of SQL and its...
March 21, 2011 at 9:07 am
NO SQL is the answer. Industry badly needs a new database model to replace the ageing and inadequate SQL model that we have been stuck with for 30 years.
SQL's longer...
March 20, 2011 at 5:35 am
SQLkiwi (1/26/2011)
January 26, 2011 at 7:17 am
I assume you have a separate database environment for your developers and that they need to create database objects like tables and procs. In that case the main role they...
January 20, 2011 at 6:26 am
It's a very well constructed piece but the approach to keys also bothers me. The article constantly refers to "the key" and dependencies on that one key. As a primer...
January 18, 2011 at 1:26 pm
PaulB-TheOneAndOnly (12/27/2010)
sawantpl@gmail.com (12/27/2010)
January 12, 2011 at 11:35 am
amarsale (12/6/2010)
December 10, 2010 at 4:33 am
True, but with MD5 the chance of an accidental collision is less than the chance of a duplicate GUID and most people don't worry too much about that. It's probably...
December 3, 2010 at 7:00 am
A hash makes a good key for the situation you have described, even more so if you can search on it (bearing in mind the other columns won't be indexed)....
December 3, 2010 at 6:43 am
I generally try to avoid triggers which modify data. Triggers that modify data can make it very dfficult to perform maintenance and development and they obscure code that ought to...
November 22, 2010 at 2:16 am
Make sure that your database design uses consistent and properly chosen data types. Apply recognised standards or carefully designed encoding schemes and business keys. Avoid using nulls. Enforce all the...
November 20, 2010 at 1:23 am
RonKyle (11/10/2010)
dbo.Rental {PK[id], FK_itemid, FK_custid}
-or-
dbo.Rental {PK[FK_itemid, FK_custid]}
In this case, I think the first works better. I don't care if a particular...
November 12, 2010 at 1:37 pm
Viewing 15 posts - 136 through 150 (of 432 total)