Timeline for How many operations SQL Server support per connection
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 9, 2020 at 4:37 | vote | accept | Frank Martin | ||
| Apr 8, 2020 at 12:22 | comment | added | Dan Guzman | The common using/open/execute pattern handles multiple threads well and leverages connection pooling too. | |
| Apr 8, 2020 at 12:20 | comment | added | Frank Martin | You may be right. I think using a using block would be much better than using a single connection. | |
| Apr 8, 2020 at 12:12 | comment | added | alroc | Why are you limiting yourself to a single connection? A connection pool would be safer and probably require less effort on your part (as there are libraries, etc. that have already implemented them). | |
| Apr 8, 2020 at 12:05 | answer | added | mustaccio | timeline score: 3 | |
| Apr 8, 2020 at 12:04 | comment | added | Jonathan Fite | What is the CPU, Memory and disk performance for this server? What are the actual queries being run? What is the exact schema (including indexes, triggers, etc.) for the database? Is your database supporting only transactional workloads or must it also support analytical/reporting? .... There are a LOT of variables. But I would guess at easily hundreds. | |
| Apr 8, 2020 at 11:54 | history | asked | Frank Martin | CC BY-SA 4.0 |