Tag Info

New answers tagged


If you create one per query / transaction, it is much easier to manage "closing" the connections. I can see why common sense dictates that you should open one and use it throughout, but you will run into problems with dropped connections and multi threading. So your next step will be to open a pool, say of 50, connections and keep them all open, doling them ...


If you have a lot of content, you should split that to several SiteCollections. You can then move those SiteCollections to more than one ContentDatabase. So you are able to keep those databases under the recommended limit of 200GB. If you think about your initial sizes and autogrowth, you should think about the growth of your content. You already mentioned ...

Top 50 recent answers are included