Which is better single database call or multiple database calls?
Less round trips between you and the DB, less processing involved. Less data transfer for the recordsets (well, only a little). Testing the performance. You can obviously test it programmatically – your client app can write the start/stop times between the 2, that’s easy and shows the performance difference from a client point-of-view.
Which is faster single Call or multiple calls?
A single call will always be faster than several calls for the same data. Simply the network turn around and latency alone is a component, but also the start up and tear down of the SQL processing will have some impact. What is heavier – a pound of apples or a bike?
Can a computed column be persisted in SQL Server?
The result of a non-nullable referenced column may be NULL in certain conditions to avoid possible overflows or underflows. You can provide an alternate value for NULL using the ISNULL (check_expression, constant), if required. For SQL Server 2000 you can not create a persisted computed column.
Can a single query be faster than another?
Queries aren’t equal. You cannot just compare them by numbers. A query must be sensible in the first place. Doing its job the best way possible, not being imaginably “faster”. That’s the only reason to prefer one query to another. I hope you meant different queries, not just a single query called 10 times.
Why does the API make calls to the database?
The API would make calls to the database. One theme that recurs in our discussions is performance: some people on the team believe that you should not have multiple database calls (usually reads) from a single API call because of performance; you should optimize them so that each API call has only (exactly) one database call.
What does it mean to have one database and one load balanced server?
If you combine those into a single call (like a stored procedure) just for the sake of only calling the database once, you have forced yourself to use the database for something which the app server might be better at. Load balancing: You have 1 database (presumably) and multiple load balanced application servers.