meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 2 months |
| seen | 8 hours ago | |
| stats | profile views | 73 |
|
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? |
|
Aug 12 |
answered | Suggestion for Large SQL Server Database Design |
|
Aug 11 |
comment |
Guidance for using composite keys to identify rows @X-Zero, I did make the point about foreign key references in my second para. The question as I read it is whether to implement the composite key, not whether also to have an auto-increment. |
|
Aug 11 |
comment |
Why is it a bad practice to allow everyone to use the sa login? Your applications do not require it. Please tell us why you think they do. |
|
Aug 10 |
answered | Guidance for using composite keys to identify rows |
|
Aug 4 |
comment |
Why does = NULL not work in Oracle? Oracle does not treat null as meaning that a value is unknown. Don't confuse the logical truth-value UNKNOWN with the missing value marker NULL - they are different things. |
|
Jul 24 |
answered | What are the alternatives for an ORDER BY clause in a View? |
|
Jul 12 |
answered | Pros/Cons Using multiple databases vs using single database |
|
Jul 7 |
answered | Which DBMS are fast enough for an online game (few thousand players)? |
