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 |
|
ngudger2021
Starting Member
1 Post |
 Posted - 2014-11-06 : 07:53:09
|
| Hi Guys,i am struggling to get my head around sql. my gf has a catalog where friends and family order from and im always reminding them how much there payments are. so my idea was to make a website where they can log into and see what there next payment is. i can deal with the website but have no idea on how to set up a database.key points is,1. they pay monthly 2. some users may have more than 1 item 3.there is a maximum credit limit for the whole account and not just the user.Could anyone point me in the right Direction for the database.Cheers guys. |
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
Posted - 2014-11-06 : 09:06:45
|
| Start thinking about how you might represent the data as a series of spreadsheets. One might contain information on people. Another might have info on products. Still another might have information on orders. Others may come to mind. Now, think of how you would link these up -- that is some person has some orders of some products -- to show what they owe. When you get that far, you have the rudiments of the tables you need to define in your database.While you're at it, download and install the free AdventureWorks database from Microsoft. Though it may be overkill for your application, it is a full implementation of a (fictitious) business with typical tables and queries. I think as you examine that design, you will see how to design your own database. You may even borrow liberally from the AdventureWorks design and tweak it to fit your scenario. |
 |
|
|
|
|
|
sql Payments system