Let's assume kramers meant an insert followed by updates. That's still a bad idea: one complete insert gives the DBMS the opportunity to optimize the layout and distribution of the records from the get-go. Breaking the insert up could cause a less-than optimal distribution of data. The later updates could cause page faults, which would result in the DBMS needing to reorganize the data, thus doing more work than a complete insert.
I'm afraid I didn't explain myself very well. Let me try this again.
I have a database of information about one object. That object has about 65 attributes.
I could create one table and store all 65 items at once in a single insert statement or I could create about 10 or 11 tables and store different values (via several insert statements)
I'm wondering which would be more efficient
Example:
Storing information about a ball
One table method (tblBall)
BallNumber, Size, Speed, Direction, Color, NumberOfValves, IsSpherical, SportUsedIn, NumberNeededForSport, etc.
Multiple table method
(tblGeneral)
BallNumber, Size, Color, etc.
(tblMovement)
BallNumber, Speed, Direction
(tblSport)
BallNumber, SportUsedIn, NumberNeeded
etc.
I've temporarily made multiple tables to organize data and because in my limited experience a long query can take longer than several short ones.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.