2009/12/16 DanV <[email protected]>: > Thanks a lot for the quick answer. > I'm using session per conversation pattern in a WinForms MDI app and > since there are customers having CAL licensing for MSSQL server the > number of connection that the application is opening is critcal.
Are you sure about that? I cannot find any information suggesting that the number of User CALs affect how many concurrent connections you can have. I do find statements similar to this: "...for example, if you have one user connecting to a SQL server from 2 different machines, you would need 2 SQL Server Device CALs or 1 SQL Server User CAL. " which to me seem to suggest that CALs are about the number of persons, not the number of connections. Another case supporting this theory is that "multiplexing", i.e. putting a web server in front of the sql server would still require one user cal for each user of the web app. > No > multithreaded involved. > > I have to admit I had completelly forgotten about ADO.NET connection > pooling since I started using ORMs :) > I also missed the fact that there is out there (in NH) an connection > release mode and it defaults to AfterTransaction which basically means > that only one connection will be used in a single threaded app. The licensing issue above should still be sorted, because if you turn off connection pooling while using a pattern where the connection will be released (that is closed if no pooling) and reopened "all the time" would probably be negative for performance. /Oskar -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
