Forum Replies Created

Viewing 15 posts - 136 through 150 (of 432 total)

  • RE: NoSQL is Not the Answer

    Revenant (3/21/2011)


    David Portas (3/21/2011)


    The problem you describe is generally harder than it needs to be in SQL for at least three reasons: SQL's appalling "recursive query" syntax; SQL's lack of...

  • RE: NoSQL is Not the Answer

    Revenant (3/21/2011)


    In my experience, the problem is not that SQL is an inadequate tool for handling RDBMS -- the problem IMO is that RDBMS is inadequate for many business tasks....

  • RE: NoSQL is Not the Answer

    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...

  • RE: NoSQL is Not the Answer

    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...

  • RE: NoSQL is Not the Answer

    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...

  • RE: An Introduction to Database Design

    SQLkiwi (1/26/2011)


    The only reason I would encourage someone to read Fabian Pascal's work is for entertainment value: his relational zealotry escalated to self-parody long ago. Others cover the same...

  • RE: Roles For Sql Developers

    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...

  • RE: An Introduction to Database Design

    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...

  • RE: Does database desingning means normalization? How much weightage goes for it in DB Design?

    PaulB-TheOneAndOnly (12/27/2010)


    sawantpl@gmail.com (12/27/2010)


    3- Different definitions of 1NF, 2NF and 3NF in different documents? really? I know there are good and bad documents in the net but failing to properly define...

  • RE: indexes for table in Relational db, what in Mutidimensional db ?

    amarsale (12/6/2010)


    this probably is a silly question but i am curious to know that if there exists an index for a table in Relational db to make query processing faster...

  • RE: Computed column as a primary key?

    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...

  • RE: Computed column as a primary key?

    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)....

  • RE: More Triggers

    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...

  • RE: Design application database with BI in mind

    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...

  • RE: many-to-many overkill: why not one-to-many???

    RonKyle (11/10/2010)


    Consider the video store. Which works better:

    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...

Viewing 15 posts - 136 through 150 (of 432 total)