|
What do I have to consider in database design for a new application which should be able to support the most common relational database systems (SQL Server, MySQL, Oracle, PostgreSQL ...)?
Is it even worth the effort? What are the pitfalls?
Started by splattne on
, 18 posts
by 17 people.
Answer Snippets (Read the full thread at stackoverflow):
What you need....
These are the wrong answers and only lead to pain interpretations .
They will often say only talk to the database via stored procs to abstract out any sql.
Is to not use database specific sql and just code to ansi standards.
|
|
What tools do you use that may be considered rare in that aspect that you have only seen a few people use it? It may be any tool that may be valuable for programmers.
I myself use UPX on occasions.
Started by DanielSwe on
, 59 posts
by 58 people.
Answer Snippets (Read the full thread at stackoverflow):
Of course, something I think is rare can actually be used by lot of programmers! Stuff tool with it, a little form to....
Internet Explorer 6.0
(Ok, it isn't rare, but it should be)
I am using PL/Scheme to write, packages etc.
AVPython.
|
|
How do you handle the storage of passwords that, by nature of their usage, you can't expect administrators to memorize? Such as:
Administrator/root password when everyone logs on using their own account with administrator rights Service account passwords...
Started by boflynn on
, 8 posts
by 8 people.
Answer Snippets (Read the full thread at serverfault):
(hat tip: Joel )
There is no reason that the password database file can't be kept on a network share the passwordsafe database in a folder shared by....
I keep the database file on a DropBox volume, so it is accessible from anywhere.
|
Ask your Facebook Friends
|
It is a bit strange to me about database schemas sample which I think most of the projects will need to design a database for it. but when I try to find sample online, it is really rare (eg. full database schema for Inventory Management, School Management...
Started by pang on
, 4 posts
by 4 people.
Answer Snippets (Read the full thread at stackoverflow):
And here's....
Marc
Why-list on database schemas.
SQL Server 7/2000 schipped with "pubs at finally getting rid of using the notorious Northwind database for demos) on Codeplex.
There are plenty of database schemas out there, I'd say.
|
|
The Media Wiki database Schema, here , has taught me a lot.
Cannot-understand: In contrast, it seems rare that other services of the size, such as Youtube, publish their database schema. Oddly, some of such services have presently opened APIs, but not...
Started by Masi on
, 4 posts
by 4 people.
Answer Snippets (Read the full thread at stackoverflow):
Generally the schema can be open to change in the future, whereas... .
Its often not relevant to an API.
Data storage is often just an Implementation detail.
You then can't change it.
What if you publish the schema, and your users become dependent on it .
|
|
Ok, dumb question I know but I see the nebulous comment 'a large database' as well as small and medium and I wonder just what that means. Can someone define what a small, medium and large database is for us SQL neophytes?
Started by Randin on
, 9 posts
by 9 people.
Answer Snippets (Read the full thread at stackoverflow):
A big database....
A medium database is one where queries take longer than one second if you don't have an appropriate index in place.
A small database is one where indexes don't matter.
One way to figure it is by observing your test queries .
|
|
I would like to know from the experienced programmers what they consider to be the most important considerations when designing a new database.
Started by Cunners on
, 13 posts
by 13 people.
Answer Snippets (Read the full thread at stackoverflow):
No duplication; store data in one be a surrogate primary key.... .
One of the most important be defined in the database (not solely enforced by the application).
Once you know your entities, they translate into database tables.
Sense.
|
|
Modern Databases systems today come with loads of feature. And you would agree with me that to learn one database you must unlearn the concepts you learned in another database. For e.g. each database would implement locking differently than other. So ...
Started by Krantz on
, 7 posts
by 7 people.
Answer Snippets (Read the full thread at stackoverflow):
Personally, I think you should know how databases workI think a developer should have a fairly good grasp of how their database system works, not matter model do not change from....
Implications when it comes to the database.
|
|
I infrequently (monthly/quarterly) generate hundreds of Crystal Reports reports using Microsoft SQL Server 2005 database views. Are those views wasting CPU cycles and RAM during all the time that I am not reading from them? Should I instead use stored...
Started by Zack Peterson on
, 5 posts
by 5 people.
Answer Snippets (Read the full thread at stackoverflow):
If you know you will be looking at the same data all.
That you run often with preset parameters.
|
|
Whether we like it or not, many if not most of us developers either regularly work with databases or may have to work with one someday. And considering the amount of misuse and abuse in the wild, and the volume of database-related questions that come ...
Started by Aaronaught on
, 24 posts
by 22 people.
Answer Snippets (Read the full thread at stackoverflow):
As for the question itself :
Every database developer should know out of their customers for....
Every developer should know that this is false: "Profiling a database operation is completely of the real world, etcetera etcetera.
|
