I need to know if it is advantageous to use Microsoft Enterprise Library. I'm gonna use it mainly for it's Data Access Application Blocks. My web application needs to access 3 SQL Server (only) databases, one of which for almost all database accesses and
the other two at specific points of a process.
I also want to know how the enterprise library handles the connection to the database, i.e. does it automatically open and close the connection by using the DatabaseFactory.CreateDatabase method and a dataset to be filled with the results? Does it handle
the multiple simultaneous database accesses?
what is the difference between using DAAB and old fashion open connection- execute command - close connection In terms of performance and load of database connections?
I think you should use the Enterprise library. The main reason we use is, so we do not have to duplicate the code and also the trust we have in it, because it has gone through the critical eye of a bigger audience (Patterns and Practices developers and general
public developers). Also, it gives a uniformity across our applications, so each app wouldnt have its own database access code. But, this article explains the reasons much better than I do.
Member
7 Points
176 Posts
Should I use Microsoft Enterprise Library
Oct 18, 2010 04:30 AM|leila|LINK
Hi everyone,
I need to know if it is advantageous to use Microsoft Enterprise Library. I'm gonna use it mainly for it's Data Access Application Blocks. My web application needs to access 3 SQL Server (only) databases, one of which for almost all database accesses and the other two at specific points of a process.
I also want to know how the enterprise library handles the connection to the database, i.e. does it automatically open and close the connection by using the DatabaseFactory.CreateDatabase method and a dataset to be filled with the results? Does it handle the multiple simultaneous database accesses?
what is the difference between using DAAB and old fashion open connection- execute command - close connection In terms of performance and load of database connections?
Thank you so much for your help in advance
Member
310 Points
152 Posts
Re: Should I use Microsoft Enterprise Library
Oct 18, 2010 09:17 AM|Alpesh Patel|LINK
Hi,
Its good to use the precompiled clsses for database operations. It cut downs a lot of overhead
Alpesh Patel
http://www.radhesoftech.com
Member
7 Points
176 Posts
Re: Should I use Microsoft Enterprise Library
Oct 18, 2010 09:53 AM|leila|LINK
Thanks for your reply,
Still ambiguous!
Member
7 Points
176 Posts
Re: Should I use Microsoft Enterprise Library
Oct 19, 2010 11:43 AM|leila|LINK
Any other explanations?!!!
Contributor
5741 Points
2608 Posts
Re: Should I use Microsoft Enterprise Library
Oct 19, 2010 12:01 PM|Kumar Reddi|LINK
I think you should use the Enterprise library. The main reason we use is, so we do not have to duplicate the code and also the trust we have in it, because it has gone through the critical eye of a bigger audience (Patterns and Practices developers and general public developers). Also, it gives a uniformity across our applications, so each app wouldnt have its own database access code. But, this article explains the reasons much better than I do.
http://msdn.microsoft.com/en-us/library/ff664416%28v=PandP.50%29.aspx