6,462 reputation
1921
bio website mooseware.ca
location Mississauga, Canada
age 52
visits member for 3 years
seen yesterday

I'm a professional software developer with more than twenty years of experience across many industries and the entire systems development lifecycle. I'm the principal consultant at Mooseware Limited.

@joelabrown

google

facebook

linkedin


Sep
15
answered How to represent foreign key in an ER diagram?
Sep
13
reviewed Edit suggested edit on Control Query Time
Sep
13
revised Control Query Time
formatted code
Sep
7
reviewed Approve suggested edit on Best practice database design - user rating tables
Sep
7
answered Best practice database design - user rating tables
Sep
6
comment Need Help in DFD Diagram for online hotel booking system
Data Flow Diagrams are well suited to documenting systems where data is stored in files or systems where there is some ETL involved. In a transactional system built on a relational database, your data doesn't "flow" anywhere. The only information in your DFD is actors and actions. What you want is probably more something like a Use Case Diagram, not a Data Flow Diagram.
Aug
30
comment How to store user's language knowledge (150+ languages) in mysql DB
Correlated sub-query is the way to go as far as clarity of code is concerned, but are your sub-queries correlated? Shouldn't it be more like: from dbo.user A and WHERE user_id = A.user_id ?
Aug
29
reviewed Approve suggested edit on DB2 Materialised Query Table performance problems
Aug
28
awarded  Yearling
Aug
23
comment Is one-to-one relationship normalized?
@Gili - re: the cost of joins: There is no right answer to that question aside from "it depends". Join cost is impacted by many factors. Whether they are negligible is even harder to answer, because that is ultimately subjective. The best way to answer you question is to mock up some test data and do volume testing. Try it both ways and see if you can tell the difference using real world data volumes (whatever that implies for your application).
Aug
22
comment Is one-to-one relationship normalized?
@Gili - If your assumption were true then this case wouldn't apply. Segregating large and infrequently needed columns allows more rows to fit on a page, thereby allowing faster retrieval of the commonly used columns. Obviously reading the segregated columns along with the commonly used columns would be slower since a join is necessary.
Aug
12
answered What's the use of assigning foreign keys on MySQL
Aug
6
answered Split date time, with only time, into minutes and seconds
Aug
4
reviewed Approve suggested edit on SSIS - Multiple data source and single excel destination, causing SqlDumper error
Aug
4
reviewed Approve suggested edit on sql-server-2012 tag wiki
Aug
4
reviewed Approve suggested edit on sql-server-2005 tag wiki
Aug
4
reviewed Approve suggested edit on IF IS NULL then SINGLE else keep the value of the field
Aug
4
reviewed Approve suggested edit on select rows where column contains same data in more than one record
Aug
2
answered Messaging Database - How to handle multiple recipients
Aug
1
comment Struggling with normalisation (database design critique)
The way you've pictured it works, as long as clients and sites can potentially have more than one contract and contracts are only ever for one site or one client. You also need to add constraints or logic to enforce that a contract is for either a client or a site. If these cardinality rules aren't what you intend, then you might need to change your design.