SqlConnection - to keep around or dispose
Database
2
Posts
2
Posters
0
Views
1
Watching
-
Imagine an app that where modification of values in the GUI are immediately updated to a SQL database. Given this scenario, would you still open and dispose of a SqlConnection object for each update? My guess would be yes because the real connection to the database should be managed via connection pools. Any rationale for either tactic would be greatly appreciated.
-
Imagine an app that where modification of values in the GUI are immediately updated to a SQL database. Given this scenario, would you still open and dispose of a SqlConnection object for each update? My guess would be yes because the real connection to the database should be managed via connection pools. Any rationale for either tactic would be greatly appreciated.