1,955 reputation
714
bio website
location
age
visits member for 3 years, 11 months
seen 23 hours ago

Oct
19
answered Is DB Normalization done purely based on the primary key or is it done based on all the candidate keys?
Oct
18
comment Should you design the database before the application code is written?
@FabriciO, It depends on the project and many other factors. I disagree that DB changes mean a failure to capture business rules or that the database was not well designed.
Oct
17
comment Should you design the database before the application code is written?
@Fabricio, in an Agile project you do not know for sure what is coming in future sprints. Change doesn't mean failure. If you try to anticipate too much then you create more work for yourself and potentially others too - and put the sprint objectives at risk. You might be able to build stuff in advance but you'd be unwise to assume things will remain static.
Oct
14
answered What are the performance considerations between using a broad PK vs a separate synthetic key and UQ?
Oct
14
comment What are the performance considerations between using a broad PK vs a separate synthetic key and UQ?
+1 for the point that performance has nothing to do with primary keys and everything to do with indexes.
Oct
12
comment Should you design the database before the application code is written?
Your data models change whenever your business changes. If your business isn't changing then it is probably dying. Nothing should ever be "etched in stone".
Oct
12
comment Should you design the database before the application code is written?
Some upfront thinking may be useful but attempting to define the whole model in advance is usually counterproductive. The model should align with business requirements and fit with project deliverables (app included) as they evolve. You cannot and should not expect those things not to change. Also creating the whole model upfront can actually obstruct other development because of the need to create dummy interfaces to support as-yet unused parts of the schema.
Oct
11
comment Should you design the database before the application code is written?
@RolandoMySQLDBA, you are assuming that a database design built during app development will be a poorer design than one built before? Why? The opposite is often true.
Oct
11
answered Should you design the database before the application code is written?
Oct
11
comment Should you design the database before the application code is written?
Adding lots of new requirements during the course of a project isn't "inappropriate". It's something that your development methods ought to support and encourage www.agilemanifesto.org/principles.html
Sep
23
comment Should you ever not assign an unique ID to each row in a table?
Poorly worded question. ID is usually short for "identifier". In a relational database we call them Keys. Are you really asking whether to create tables without keys?
Sep
2
answered Why is there still a varchar data type?
Aug
29
comment VLDB - SQL SERVER versus VFoxPro
SQL Server isn't "100 times slower than VFP" you aren't comparing like for like and you aren't really measuring anything that's useful for your specific problem. E.g. consider where your data will be sourced from. I suspect it may not be coming from an incrementing variable in a loop which is located in memory on the same machine as the database. Think about the entire architecture you need - not just the database component of it.
Aug
29
answered VLDB - SQL SERVER versus VFoxPro
Aug
21
comment Normalization: Is it considered compliant to split static, numeric values like a year into their own table?
@jcolebrand: Agree with what you say. Still the answer to the question is the same: whether you do it or not has nothing to do with normalization per se.
Aug
21
answered Normalization: Is it considered compliant to split static, numeric values like a year into their own table?
Aug
21
answered Is Oracle more demanding environment for a DBA than SQL Server?
Aug
20
comment Is there a DBMS that allows the “= NULL” syntax?
Be aware that the ANSI_NULLS OFF option changes the meaning of certain expressions. You can break or change the behaviour of your code just by changing the ANSI_NULLS option. Also certain SQL Server features are disabled when ANSI_NULLS is OFF. ANSI_NULLS OFF is a deprecated feature and really should be avoided unless it's essential for backawards compatibility reasons.
Aug
14
answered When should you denormalize?
Aug
12
answered Policies RE database triggers in well-designed applications?