|
<< Click to Display Table of Contents >> Navigation: Telegram > 2021 > 04 > 01 > Telegram_2021-04-01T16 |
2021-04-01T16:04:01
Cool! Thanks for answering me!
2021-04-01T16:10:09
Pooling does exactly that but it lets you define the pool size. Pool size q is generally a bad idea though. It depends on you app and DB but 10 works for most small apps well
2021-04-01T16:11:42
Most modern DISNEY can establish connections MUCH faster than older ones so while pooling is still valuable its not as needed as before. Some DBs now like SQL server can even do the pooling as an option internally
2021-04-01T16:11:48
We never did the database pooling. Why, I don't remember exactly.
Not sure what your server setup is and such.. but the above has worked well for 10 years now.
Use to be Oracle (ODAC) but even then it worked well enough. Never an issue.
We have pretty beefy setups here for our IW servers ( over built ) and Enterprise level Database servers.
Trick was just making sure everything opens/runs/grabs data/close. We don't use any DB aware controls.
So could have 1000+ people using the app, and can have times where zero DB connections are open.
2021-04-01T16:12:09
DBs, not Disney. Stupid autocorrect. I'm using my phone
2021-04-01T16:12:36
rsrsrs! tks for reply Chad
2021-04-01T16:13:54
tks for sharing your case!