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 |
|
maya_zakry
Constraint Violating Yak Guru
379 Posts |
 Posted - 2007-06-19 : 00:15:44
|
| hi all..if im about to start a new database.. how do i start?please advise on how do i start sketching a new db structure... how do u guys set up ur db table struc.. any software to do this designing? any links or tutorial will be appriciated..~~~Focus on problem, not solution ¯\(º_o)/¯ ~~~ |
|
|
LoztInSpace
Aged Yak Warrior
940 Posts |
Posted - 2007-06-19 : 03:57:43
|
| There are many tutorials, courses and books out there but unfortunately I can't reccomend one in particular. What I want to warn you against though is jumping in too early.You need to understand the fundementals of database design & relational theory before even considering it or you'll end up with a bunch of crap, so whatever you do do not get any "software to do this designing". It may help you create the scripts but if you don't understand the theory behind it the software will only get you into the mess slightly faster.It's not something you can learn overnight (or in 21 days or whatever the latest series is). Unfortunately there are things that require work & study. That said, you can check the MS Access forums and get quite a different answer :) |
 |
|
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2007-06-19 : 09:54:04
|
| Your first step has nothing to do with databases. Close Query analyzer, SSIS, Access, whatever you have open. Grab a piece of paper. Then map out the LOGICAL model that you will be creating a database for. The logical model is just the business model -- what you are storing, how things relate in general, parent/child relations between entities, and so on. Your first step has nothing to do with any database model at all -- it is mapping out the business requirements. This is the hardest part of data modeling -- understanding and listening CAREFULLY and thinking ahead and asking questions and learning WHAT you are trying to model from a 100% business perspective.Only when that is done and agreed upon and verified by the users should you then move on to implementing that model as a physical database model consisting of tables and such. And, if you did a good job in step 1, then step 2 is usually quite easy. But step 1 -- the logical business model -- is the most crucial and most difficult part when doing ANY sort of software engineering, be it a website, a desktop application, or a database.- Jeffhttp://weblogs.sqlteam.com/JeffS |
|
|
|
maya_zakry
Constraint Violating Yak Guru
379 Posts |
Posted - 2007-06-19 : 22:20:33
|
| thanks for the advise.. yea.. designing has never been easy..i have this system requiremnets to start the flow chart...and if anyone has any exp designning some accounting web based do let me know...~~~Focus on problem, not solution ¯\(º_o)/¯ ~~~ |
|
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2007-06-19 : 22:44:23
|
Since you are designing a quite standard application, you should / need to have some basic knowledge on accounting. If you have no idea what is debit / credit (beside your bank account), i would suggest you try to gain (from books, web etc) some knowledge on basic accounting then talk to your in-house accounts dept staff / accountant / financial controller etc to find out further details.
KH |
|
|
|
maya_zakry
Constraint Violating Yak Guru
379 Posts |
Posted - 2007-06-20 : 02:03:41
|
| ... studying accountinfg huwaaaaaa~~~Focus on problem, not solution ¯\(º_o)/¯ ~~~ |
|
|
|
|
|
|
|
|
design db structure