is there a "rule of thumb" that will tell us whether we should use com+ for our db transactions or not? We are converting a system from com/vb to .net. I am trying to figure out whether we should just keep our transaction layer in ado.net, the sproc level, or use com+ through system.enterpiseservices. It is an interal intranet app, we are not concerned with multi db (just sql 2k) platforms, or anything like that. Our biggest concern is supporting concurrent connections to db of about 200+.
Can someone give me some do's and don'ts based on (managemnet, development time, performance overhead, etc..) based on your expreience or research, or a link to a good article. I have a meeting in two hours where we will begin the planning phase of this and layout the initial design alternatives. thanks. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
