DataBase Design For InvoiceSystems

Sir I am doing my Final Year B.sc(Comp.sci), I am having my Oracle Project to do things.
I just wan't a Detailed DataBase Design for
Invoice Systems
Please Could you help me in terms of DataBase Design......

The best way to approach a database design is to write a
specification for the application. Document what processes the help
desk technicians will do. In the process, identify what pieces of
information they work with. When you have the complete
specification written, you can then begin grouping the pieces of
information they work with together. For example, a ticket may have
a number, status, priority and a person to whom it is assigned. The
person to whom the ticket is assigned will have a name, phone
number, e-mail address and a list of technical skills.
So in this overly-simplified example, we could have a table
that contains ticket information, a table that has information
about technicians and a table of skills. Then ask your self
questions like "Can one ticket be handled by more than one
technician?" "Can one technician handle more than one ticket?" Can
a technician have more than one skill?" In this way, you can begin
seeing the one-to-one, one-to-many and many-to-many relationships
that exist.

Similar Messages

Database design for share market

Hi One and All,
I have a query regarding, design of New database....
Right now I joined as a Database administrator as a fresher, my superior has given me one assignment i.e. I have to create a sample database on Share market. As per his requirement the tables should be Issuer table, Security table, Broker table, INvestor table, Account table, Order table, Tradeing table. He said that I have to prepare the fiellds for this tables and relation ships and whole database structure.... I can prepare relations ships and database structure but the problem is, I don't know how the stock market is really works. If any body help me in this issue I am very thank full to him.
I need just the table feilds, if I get this rest of job i wil do by studying the subject of share market.
Thank You

Hi,
As per Hemant this forum is not appropriate for this question. However you have to analyze the system by meetings with stock broker at stock Exchange or to the client for which you are designing the system. Ask your superior to arrange meeting with client and then ask question to him so that you can made database design for them.
Regards,
Abbasi

Database design for Help Desk application.

Hello does any one know
Database design for Help Desk application.
ERD
Business rules and features
?

The best way to approach a database design is to write a
specification for the application. Document what processes the help
desk technicians will do. In the process, identify what pieces of
information they work with. When you have the complete
specification written, you can then begin grouping the pieces of
information they work with together. For example, a ticket may have
a number, status, priority and a person to whom it is assigned. The
person to whom the ticket is assigned will have a name, phone
number, e-mail address and a list of technical skills.
So in this overly-simplified example, we could have a table
that contains ticket information, a table that has information
about technicians and a table of skills. Then ask your self
questions like "Can one ticket be handled by more than one
technician?" "Can one technician handle more than one ticket?" Can
a technician have more than one skill?" In this way, you can begin
seeing the one-to-one, one-to-many and many-to-many relationships
that exist.

DataBase Design For Library maintenance

Sir I am doing my Final Year B.sc(Comp.sci), I am having my Oracle Project to do things.
I just wan't a Detailed DataBase Design for
Library Maintenance
Please Could you help me in terms of DataBase Design......

Suyambu
You have asked several questions of this nature.
A forum cannot be expected to take the place of a comprehensive book or training course.
Please ask reasonable questions about distinct issues which can be given succinct replies.

DataBase Design For Library maintanence

Sir I am doing my Final Year B.sc(Comp.sci), I am having my Oracle Project to do things.
I just wan't a Detailed DataBase Design for
Library Maintanence
Please Could you help me in terms of DataBase Design......

Suyambu
You have asked several questions of this nature.
A forum cannot be expected to take the place of a comprehensive book or training course.
Please ask reasonable questions about distinct issues which can be given succinct replies.

DataBase Design For Inventory Systems

Sir I am doing my Final Year B.sc(Comp.sci), I am having my Oracle Project to do things.
I just wan't a Detailed DataBase Design for
Inventory Systems
Please Could you help me in terms of DataBase Design......

The best way to approach a database design is to write a
specification for the application. Document what processes the help
desk technicians will do. In the process, identify what pieces of
information they work with. When you have the complete
specification written, you can then begin grouping the pieces of
information they work with together. For example, a ticket may have
a number, status, priority and a person to whom it is assigned. The
person to whom the ticket is assigned will have a name, phone
number, e-mail address and a list of technical skills.
So in this overly-simplified example, we could have a table
that contains ticket information, a table that has information
about technicians and a table of skills. Then ask your self
questions like "Can one ticket be handled by more than one
technician?" "Can one technician handle more than one ticket?" Can
a technician have more than one skill?" In this way, you can begin
seeing the one-to-one, one-to-many and many-to-many relationships
that exist.

Help with a database design for community housing project

Talking database design
Hi all, I have been wondering about the design of tables for a big block of residential units. There are 100 + rooms. there are about 25 houses in this complex but the 100 + rooms are all rented out separately.
Its just like a college campus really but its not a college campus , its a little unique.
The rents are applied as a percentage of income, so thats not common, so I included a tblRoomCost where the pre-calculated weekly cost is entered, and its got a date field in there for when the change of rent charged. I probably need to include an income field in tblCustomer, even just as an Admin reference.
So is this looking pretty ok and would there be any point in scrapping the database and using text files ?
So what do you think of these tables please ?
tblCustomer
pkCustomer, fldFirstName, fldLastname
tblRoomAllocation
pkRoomID, fkCustomer
tblRoomCost
pkRoomID, fldDate, fldRoomCost
tblTransactionID
pkTransactionID, fldDate, fldTransactionType, fkCustomer, fldAmount

The naming scheme is one I learned and havn't thought past it though I do get into trouble and your suggestion may prove useful when codeing !
I thought the tblRoomAllocation and tblRoomCost took care of changing. Though I see now that tbleRoomAllocation needs a Date field really. And the tblRoomCost has a fldRoomCost which isnt really that good an implementation as the rooms themselves are priced always accoedijng to the income of a resident and not because of the room. So the real world object is getting fudgy........
It is extremely unlikly that Admin would ever allow two rooms to be rented by an individual.
I will have a look at possibly your suggestion that an Accounts table be used.
Also I thought about having a startDate and EndDate in the tblTransaction to represent the period being paid for. Just seems like a lot of Dates in a transaction table. One to record the transaction, the other two dates to indicate the period that was actually being paid for. ? When perhaps I should work that out in the runtime code.v ? This will be a VB.Net app.
Do you think there is a need for Accounts table if only one room is permitted to be rented , though room changing may be common?
And thx for your input.
Message was edited by:
user521381

Database design for swapping/trading items between companies

What is the best SQL table schema for items being swapped/traded between companies? For instance:
e.g.1 If company A wants to swap item 0001 (owned by customer X but being managed by company A) with company B who is offering item 0002 (owned by customer Y but being managed by company B) and item 0003 (owned by customer Z but being managed by company B)
e.g.2 If company A wants to swap item 0004 (owned by customer X but being managed by company A) with company B who is offering item 0005 (owned by customer Y but being managed by company B)
These are the tables I have so have so far, it should be good enough to support 1 to 1 trades but not too sure about 1..* to 1..* (many to many) trades, is it correct or can it be improved further?
Note: Trades can only happen between two companies, but they could trade as many items as they wish.
Trade
id: int (primary key)
company1_id: int (foreign key)
company2_id: int (foreign key)
datetime: string
status: string
TradeDetail
id: int (primary key)
trade_id: int (foreign key)
item_id: int (foreign key)
Company
id: int (primary key)
name: string
address: string
phone: string
email: string
rating: int
Customer
id: int (primary key)
f_name: string
s_name: string
dob: string
address: string
phone: string
email: string
Item
id: int (primary key)
customer_id: int (foreign key)
company_id: int (foreign key)
price: double

I made a few changes.
You need to think about NATURAL KEY for each table. For example, what is the NATURAL KEY for the Customer table. It can be:
CompanyTaxID char(9) NOT NULL UNIQUE
or
SSNO char(9) NOT NULL UNIQUE
Trade
id: int (primary key)
company1_id: int (foreign key)
company2_id: int (foreign key)
datetime: datetime
unique(company1_id, company2_id, datetime)
status: string
TradeDetail
id: int (primary key)
trade_id: int (foreign key)
item_id: int (foreign key)
Company
id: int (primary key)
name: string
address: string
phone: string
email: string
rating: int
Customer
id: int (primary key)
f_name: string
s_name: string
dob: string
address: string
phone: string
email: string
Item
id: int (primary key)
customer_id: int (foreign key)
company_id: int (foreign key)
price: decimal(20,2)
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Database Design for Multiple function site

Hi
I am working on one project which involve multiple function
site, such as
Company Product Catelog, Customer Support Forum, Document
Exchange Engine and
etc...
Normally we will combine ALL TABLEs into one DATABASE.
My question are:
1) Is my break them to individual DATABASE, will it perform
better?
Means Product Catelog and Forum will have different
DATABASE, but they
will using the same DOMAIN NAME.
2) I am worried about the break down and corruption of
DATABASE, so I have the
idea to separate them out. Are my idea correct or wrong?
3) I am seeking for better DATABASE DESIGN, because I know
the database will
become huge in future. I request for your idea and opinion.
Thank you very much.

Creating views: not an option I think. It would involve a lot of programming with 'instead of' triggers etc.
Seperate databases: a good way if the locations are completely independant and do not share information. This involves more DBA work.
Separate schema's in one database: this would make public synonyms impossible, and is probably not a good option.
Adding a location id to tables: the best way I think, and flexible. You can easily add another location, and locations can easily share information.

Database design for the Project System!

Hi
I need the database design schema for the Project System .
For example with the transaction code CJ20N at the left side all the Project Hierarchy is tabulated.
I want to know the relations between tables ?
Would you please help me ?

look logical database PSJ with tcode SE36
grx. A.

Database design for DSS

Hello All
I have to design database for a DSS.
It is basically a MIS project which will be used for reporting purposes
Can anyone please tell me what are the considerations to be made
while designing for such a system.
Any documents or web links will be of great help
Thanks in advance
Ashwin N.

The best way to approach a database design is to write a
specification for the application. Document what processes the help
desk technicians will do. In the process, identify what pieces of
information they work with. When you have the complete
specification written, you can then begin grouping the pieces of
information they work with together. For example, a ticket may have
a number, status, priority and a person to whom it is assigned. The
person to whom the ticket is assigned will have a name, phone
number, e-mail address and a list of technical skills.
So in this overly-simplified example, we could have a table
that contains ticket information, a table that has information
about technicians and a table of skills. Then ask your self
questions like "Can one ticket be handled by more than one
technician?" "Can one technician handle more than one ticket?" Can
a technician have more than one skill?" In this way, you can begin
seeing the one-to-one, one-to-many and many-to-many relationships
that exist.

Database design for objects with multiple states

Context
I'm designing a database which, simplified, should be able to handle users sending job requests to each other, and after that a job can be started, finished, and reviewed. The design should be scalable (think millions of users).
Approaches I've considered:
Gargantuan table
One approach, probably not the best one, would be to simply store ALL jobs in one, huge table
jobs. This table would need a state column to represent which state the job is currently in (e.g.
ACCEPTED, STARTED, FINISHED, REVIEWED e.t.c.). The biggest problem with this approach that I can see is that jobs in different states have different types of data that are relevant to them. For example, a
job request has a preliminary agreed upon price, but that could change before the job is started, and change again before the job is finished. This could of course be solved by just adding more columns to the table and naming them properly, but it will probably
become a huge bottleneck performance-wise very early to have one table containing all the different types of possible data for all the different possible states of a job.
Different tables for different states
This approach would be to have multiple tables, for example job_requests,
jobs_started, jobs_finished, tables who in turn can have substates, e.g.
job_requests could have the sub-states PENDING, ACCEPTED, while the
jobs_finished table would have the substates COMPLETED,
CANCELLED, REVIEWED.
With this approach each table only contains data which is relevant to the current job state, but on the other hand some data might be duplicated (for example the user ids of the job requester, and job receiver -- on the other hand this information could
be stored in yet another table?). The problem with this approach is that I can't think of a good solution on how to archive all the information when transitioning between states. For example, once a job request has been accepted, and then started, it should
be deleted from the job_requests table and moved into the jobs_started table, but it's just a matter of time before a stakeholder wants to know for example how long the average time is between a job request being created, until it's
been started, at which point I'd need the data from the job_requests table to be able to calculate it.
It feels like this type of problem should be easy to solve, but I really can't think of any good solution which "feels right", any solution I come up with feels ugly and I can immediately think of a number of things which makes the solution bad.
Very grateful for any feedback or tips on approaches I could take. Thanks in advance!

This will be moved to the design fourm, which I don't monitor, by a moderator within a day or so.
A table in a relational database is supposed to model a unique entity. Job is such an entity. But "Jobs in Washingon state" and "Jobs in Oregon" are two such unique entities.
I don't see why jobs in different states would have different attributes, but it is not my business domain. And the problem certainly appears in other areas. My area is financial instruments, and they come in many flavours. And still have many attributes
in common.
So what we do is that we have a table instruments which holds common data. And then there are tables like funds, futures, bonds, optionandwarrants etc that holds attributes that unique to these classes of instruments. These specific tables are child tables
to the instruments tables.
Erland Sommarskog, SQL Server MVP, [email protected]

Database Design for use with XSQL-connected Clients

Hi all,
this might seem a little off-topic at first, but I suppose we are not the only ones reading this group designing an architechture using XSQL servlet as the only connection to the database, with clients connecting over the internet.
So far our approach works well, but of course any database round trip is much more expensive in this environment than with clients that hold an open connection to the database.
That led us to the idea of generating primary keys on the client instead of the database (e.g. with CoCreateGuid on Win32). Do those GUIDs have to be stored in the Oracle database in a RAW column or does a NUMBER field do the job?
I found a hint in the Oracle 8i Replication manual to use SYS_GUID values in a RAW(32) column as a primary key to avoid conflicts between sequences on multiple machines. But I didn't find any statement concerning the performance issues of this.
Our database will not store huge amounts of data (most tables < 100.000 rows, just a handful more than a million in huge environments, which will be able to afford huge machines...), so this should not be
a problem, I guess.
Does anyone of you have experience with this?
And another question: Can I safely assume that keys generated with SYS_GUID on the Oracle server will not likely be the same as those that are generated using CoCreateGuid on the Win32 client?
Thanks for your input.
Olaf Lewitz
ohltec SOFTWERFT, Hamburg

Don't GUID's have hyphens in them? If so, you'd have to use a VARCHAR2(xx) of appropriate length. If not, then you can likely use HEX_TO_RAW() and RAW_TO_HEX() to store then in a RAW as you've noted.
Note that the XSQL Servlet's default connection manager does to connection pooling, so the roundtrip to the database may not be as expensive as you're thinking. :-)

Database design for multiple users/connections

Hello All,
My questions are about overall design/strategy of the database.
We are using Oracle 9.2.0 on AIX as a backend for a ColdFusion application. When deployed, the CF app and Oracle will be running on our customer's server, with the customer's various physical locations accessing the server remotely. The customer will manage the oracle database on their server.
With the potential for approximately 70 locations remotely accessing the database at the same time, each remote location will only be selecting and updating their own records out of any table -- i.e. each record contains an indexed "location id" -- although inserting would be a different story.
Would creating views provide the data manipulation performance the users would need? Or perhaps individual schemas with individual tables/indexes for each location id? Or should we consider separate databases?
Does anybody have any ideas or practical suggestions about how to approach this? Are there other considerations that we should be thinking about?
Please let me know if I have not provided enough information. Your comments/criticisms are greatly appreciated.
Louise

Creating views: not an option I think. It would involve a lot of programming with 'instead of' triggers etc.
Seperate databases: a good way if the locations are completely independant and do not share information. This involves more DBA work.
Separate schema's in one database: this would make public synonyms impossible, and is probably not a good option.
Adding a location id to tables: the best way I think, and flexible. You can easily add another location, and locations can easily share information.

Database design for questionaire

Hi There
I'm wondering if anyone has examples of desigining a database for exams/etc? What I'm finding difficult is the need for multiple types of questions:
1. Multiple choice, one correct answer
2. Multiple choice, multiple correct answer
3. Text answer
4. Put items in the correct order answer
I've been trying to find an example of a database that stores different type of questions/answers
that shows how to create this type of system but yet to find one.
Is it best to create different tables for questions/answers? Different tables for different type of questions?
Or store the type of question and the answer in the one record?
Thanks in advance.
Regards,
Phanikanth
Edited by: user12000608 on Mar 9, 2010 12:50 AM

user12000608 wrote:
Hi There
I'm wondering if anyone has examples of desigining a database for exams/etc? What I'm finding difficult is the need for multiple types of questions:
1. Multiple choice, one correct answer
2. Multiple choice, multiple correct answer
3. Text answer
4. Put items in the correct order answer
I've been trying to find an example of a database that stores different type of questions/answers
that shows how to create this type of system but yet to find one.
Is it best to create different tables for questions/answers? Different tables for different type of questions?
Or store the type of question and the answer in the one record?
Thanks in advance.
Regards,
Phanikanth
Edited by: user12000608 on Mar 9, 2010 12:50 AMStart here: http://en.wikipedia.org/wiki/Database_normalization

DataBase Design For InvoiceSystems

Similar Messages

Maybe you are looking for