Need database design

I'm trying to write a simple employee Scheduling software for about 20-30 people in my software development company.we have four shifts in our company.i need a database design for these software.Please help in, what are the tables we can consider. at present i am blank from where to start. so if any help is really appreciated.
thank in advance to all folks.
Thans & regards,
Venu

Hi below is one link for database design for data warehousing
[www.tti.it/docs/deplEng/BP8-SCHMITZ%20ING.pdf]

Similar Messages

Need Database Design Links

Hi,
Please give me a few URLs or documents to understand Database Design techniques thorughly for both OLTP and Data
Warehousing projects, thank you.
Regards,
DR

Hi below is one link for database design for data warehousing
[www.tti.it/docs/deplEng/BP8-SCHMITZ%20ING.pdf]

IF Auto Update Statistics ENABLED in Database Design, Why we need to Update Statistics as a maintenance plan

Hi Experts,
IF Auto Update Statistics ENABLED in Database Design, Why we need to Update Statistics as a maintenance plan for Daily/weekly??
Vinai Kumar Gandla

Hi Vikki,
Many systems rely solely on SQL Server to update statistics automatically(AUTO UPDATE STATISTICS enabled), however, based on my research, large tables, tables with uneven data distributions, tables with ever-increasing keys and tables that have significant
changes in distribution often require manual statistics updates as the following explanation.
1.If a table is very big, then waiting for 20% of rows to change before SQL Server automatically updates the statistics could mean that millions of rows are modified, added or removed before it happens. Depending on the workload patterns and the data,
this could mean the optimizer is choosing a substandard execution plans long before SQL Server reaches the threshold where it invalidates statistics for a table and starts to update them automatically. In such cases, you might consider updating statistics
manually for those tables on a defined schedule (while leaving AUTO UPDATE STATISTICS enabled so that SQL Server continues to maintain statistics for other tables).
2.In cases where you know data distribution in a column is "skewed", it may be necessary to update statistics manually with a full sample, or create a set of filtered statistics in order to generate query plans of good quality. Remember,
however, that sampling with FULLSCAN can be costly for larger tables, and must be done so as not to affect production performance.
3.It is quite common to see an ascending key, such as an IDENTITY or date/time data types, used as the leading column in an index. In such cases, the statistic for the key rarely matches the actual data, unless we update the Statistic manually after
every insert.
So in the case above, we could perform manual statistics updates by
creating a maintenance plan that will run the UPDATE STATISTICS command, and update statistics on a regular schedule. For more information about the process, please refer to the article:
https://www.simple-talk.com/sql/performance/managing-sql-server-statistics/
Regards,
Michelle Li

Need a sample Oracle Database Design Document

Looking for a sample database design document.
Which may include below high level steps if possible.
1. Hardware & software specifications.
2. Database Sizing/ estimate.
3. Schema Design
4. Data transformations/ feeds
Thanks
Mallikharjuna

user8919741 wrote:
Looking for a sample database design document.
Which may include below high level steps if possible.
If you Google "database design document" you'll see that there are many templates available. I've never used any such document, and I think you'll be hard pressed to find one that fits your business needs exactly (assuming there are business needs behind your request).
1. Hardware & software specifications.
2. Database Sizing/ estimate.I would suggest you analyze existing workloads and base your estimates on that. If there is no existing workload you'll have to estimate one based on how many users you estimate will use the solution, or some other clever estimation method.
3. Schema Design This is a matter of translating business/application requirements to what needs to be stored in the relational database, and creating a data model based upon that. Every model will be different.
4. Data transformations/ feedsYou could simply document each transformation/feed and purpose.
Thanks
Mallikharjuna

Why would you need a database design before implementing?

Why would you need a database design before implementing?

977222 wrote:
Why would you need a database design before implementing?It appears from the 4 questions you put up ina 2 hour period
help me with this
Why would you need a database design before implementing?
Re: answer these quesions pls
answer these quesions pls
That you have put off doing your homework and now expect this forum of volunteers to do your research for you ....

Suggestion: Create a Database Design Forum

I recommend the creation of a new forum dealing exclusively with database design questions, such as setting Primary Keys, Unique constraints, Check constraints, Indexes, schema-creation scripts, etc. There is no forum devoted exclusively to this topic now and I feel it would be very helpful to the user community. It would certainly make searching for answers to design questions much easier.

Billy Verreynne wrote:
Prohan wrote:
I don't agree there.
1. How to create a relational model certainly IS relevant to Oracle, which is a RELATIONAL DBMS.Oracle also supports data warehousing (star schema designs), network/hierarchical designs, object-relational designs - or pretty much any data model that you may come up with. Calling it just a relational DBMS is incorrect.
2. Your point that logical models are independent of specific technology is correct. What you're missing is that if a specific technology makes use of a certain foundational body of knowledge, that knowledge is a legitimate topic for a forum whose users use that specific technology.That is putting the cart in front of the horse IMO.
I would rather see data modeling and logical database design being done in a way that is untainted with specific vendor implementations and technology used. There needs to be a clear line dividing the design from the implementation. If not, then design decisions can (and will) be made based not on the correct logical data modeling principles, but whether it can be "handled" by the technology. A design that is tainted like that, will always be less than optimal (especially as technology is continually evolving and changing).
An OTN forum for database design will invariable be tainted with Oracle technology - and instead of learning sound data modeling fundamentals, a warped view of data modeling will be conveyed. Where doing abc will be acceptable (when it is not), because Oracle has feature xyz that can make the flawed design work (in a fashion).Excellent points. I think (or at least hope) such a forum would attract some number of pure theorists to straighten out the view. This might make for a lively forum, and might actually influence the real products, and might even get the cart on the right side of the horse.
Hmmm, I guess I do sound hopelessly optimistic.

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

Doubt in Database Design

Hi,
I have got some doubt in database design. I am designing a database for Inventory Management. Wherein i need to store the order details in one to many relationship. I have designed my tables as follows (Just sample)
-- Tbl_OrderOne
OrderCode (PK)
OrderDate
CustomerInfo
-- Tbl_OrderMany
OrderCode (FK)
ItemCode
Qty
What doubt i have got is, since oracle has the features like creating objects and use them as data type and store the data.
Can i use this feature in this case. Here in this case trasactions will be very high. Does it affect the performance. But presently i have designed it using foreign key reference as i showed you in the beginning. If using the Objects to store that huge number of data is feasible and increases the performance, then i can go for Object type feature.
Thanx in Advance
Regards
Vinayak
null

Vinayak,
One more thing. You can check out more information about NESTED TABLE at http://otn.oracle.com/docs/products/oracle8i/doc_library/817_doc/appdev.817/a76976/adobjdes.htm#446526
Regards,
Geoff

Database design (ERD )for Inventory Management System

Dear All,
I am going to develop a simple Inventory Management System software using C# .NET for my learning. After searching different forums, many people have suggested to first create a database design for the software. I want a database design, in short, an ERD
diagram for simple Inventory Management System which shows proper entities(tables), attributes and relationship between entities.
It would be highly helpful for me as I am newbie to C# and databases.
Thanks,
momersaleem

Dear Rebecca,
Thanks for you suggestions.
As I am going to develop IMS for learning purposes so I think I wouldn't need to go in detail regarding Customer name and addresses. However, I am still thinking of adding country attribute in customers' table which I think will be helpful to sort out customers.
What's the difference between a purchase and an order? They're usually the same thing, which doesn't mean you're
wrong, but what are you picturing here? Purchase entity will be used to keep record of purchases you made and an order entity will be used to keep record of orders that cutomers placed.
Pricing:
Any order system needs to manage two very distinct bits of data that are easy to confuse. The price in the Product entity is the current
price. The price in the Order entity is the selling
price. Not at all the same thing--current price is almost certainly going to change over time. Selling price won't.
Does it mean that I'll change the price attribute for product to current_price and add selling_price to order table which will help to keep record of price at the time of order?
Why did you include a quantity field in the Products table? Is it meant to represent stock on hand?
Yes you are right. It represents stock in hand.
Could you please recheck the entities relationships as I am not confirmed whether these are correct or not?
Thanks,
momersaleem

Good database design and modelling books

Hi ,
I need to work on designing a database from the scratch by creating logical database design and then physical database design.I'm new to database design.
Can someone please point me to some good database design and modelling related books /tutorials.
Regards,
Bharath.

bharathDBA wrote:
Hi Girish Thanks for the information.
I would definitely look into this book later.
I don't mind paying any amount of money,if that book gives me the knowledge I want.
As this book is international edition,for shipping it is taking 8-10 business days and by that time I need to complete designing my database and probably I might need to some other book.
Is this a school assignment? I hope so. Referring back to your opening statement "I need to work on designing a database from the scratch by creating logical database design and then physical database design.I'm new to database design." I can only say that database design is a very big subject. If you are starting from a position of no knowledge at all, I'm afraid there is nothing that is going to give you the knowledge you need in the time frame you have. I will say you need to start by learning the rules of Data Normalization. Make your logical design Third Normal Form. Good can be your friend. There is actually a pretty good write-up on Data Normalization on Wikipedia.

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

Urgent help database design

Hi,
I need an urgent help with the design of the database, We have already a database in production but we are facing a problem with extensibility.
The client information is variant that is
1) number of fields are different for each client
2) client may ask anytime in future to add another field into the table
Please provide your views with practical implication (advantages and disadvantages) or any resource where I can find information.....
Help appreciated.....

Hi,
Database design is an art & science by itself - as far as I know, there aren't any rigid rules.
I would suggest that you have a look at the discussions in these two threads for a few general ideas :
Database Design
conversion from number to character
If your client requirements keep changing, I would suggest that you keep 8- 10 "spare" columns in your tables - just call them spare1, spare2, etc.. The only purpose of these tables is to allow flexibility in the design - i.e.., in future you can always extend the table to accommodate more fields.
I have used it a couple of times & found it to be useful - again, this is only a suggestion.
Regards,
Sandeep

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 in JDeveloper

Hi,
In JDeveloper 10.1.3.1 (existing) database can be imported (I red about it in Oracle Magazine by Steve Muench). I selected some existing tables and printed these. This works fine and looks good on paper.
I was wondering how trigger-code, functions, procedures can be imported (or created) in JDeveloper. Also, can I add storage information like tablespaces to objects?
I would like to use JDeveloper as database-design tool (therefore I need some basic 'designer' functionality)
Thanks,
Stephan

Thanks. I read the documents, interesting!
From my 'Connections' page I can create a trigger. Thats fine.
But imagine I do not have a database yet. I want to start from scratch and first create a new table having a simple trigger on it. I go to the 'Applications' page and in the 'Database Design' I drag a table from pallete. This works fine. But, how to add a trigger to this table??
Thanks,
Stephan

Database Designer App

Hi,
I need to make a database designer type application.
Where there are floating list boxes that can be moved around. Each of the list boxes will represent a tables and you can drag relationships between the list boxes which will create a line mapping the rows of the list boxes.
kinda like sql server or any type of RDB mapping tool.
Not really sure even how to start with the movable list boxes. Any suggestions?
Thanks,
-J

Nevermind, i found flexMDI which seems to work.
But not sure how to draw the lines and also be able to select the lines between the windows.

Need database design

Similar Messages

Maybe you are looking for