Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SQLIsTheDevil
Posting Yak Master
177 Posts |
 Posted - 2008-08-26 : 12:43:23
|
| I need a bit of a refresher and I was hoping I can get some answers on this forum. I'm designing a database and a web application. I have a few basic but broad-based questions. Is there a methodology that dictates how one should go about this task? For example, would one design the database exclusively and then design the web application? Or, would one design both concurrently, moving back and forth between the two? Obviously, I want both systems to be performance-friendly and user-friendly; keep things simple and compact and modular, for future-proofing. Again, how much should I base one design on the other, if at all?It's not a short answer question; so, I'll certainly appreciate any responeses. Thank you in advance. |
|
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2008-08-26 : 13:53:06
|
| The database will almost surely outlast the web application. So design a solid data model first, that could server more than one application interface. Then design the application interface to interact with the database.In OOP terms, think of the database as an object with public methods and properties. The database object should be robust and powerful enough to be called from multiple applications, and what goes on inside the object is "private" and none of the application's damn business.Boycotted Beijing Olympics 2008 |
 |
|
|
|
|
|
basics of designing a database