I've a credit card applicatoin that stores roughly 24 fields of information in regards to a machine. Shall We Be Held best getting one large SQL statement that card inserts all this information, or must i use many small claims because the date is joined?
A good example: CPU/Memory/Hard disk drive is a group, another could be client contact/phone/address. Shall We Be Held best getting information after which creating the data within the table or must i go into the first group because the information is joined, then go into the second group, etc?
The fields all will be present on a single page, and sights happen to be produced for every group.
You're best carrying out a single Place for those fields.
If things are on a single page (you've all data offered at one) do one
INSERT, otherwise you'll be doing an
INSERT after which a couple of
UPDATEs, that is always reduced (because you do a couple of operation rather than one) and much more complex that you should write. Inside your situation the rate difference is going to be minor.
For card inserts and updates, you'll most likely be superior with large card inserts, as opposed to a small place then multiple updates.
Where large queries are occasionally less capable than small ones happens when doing large, complex joins or sub-chooses. After which, you will need to test both forms to determine what is much more efficient.
You may even discover that more compact queries be more effective for card inserts and updates in rare cases when you've got a large amount of securing/contention happening, or complex foreign key associations or any other constraints.