Hot answers tagged database
If you navigate to Central Administration >> Monitoring >> Reporting: Configure Diagnostic Logging. You can configure logging to be less verbose, turn off logging for features you may not need, and limit the amount of space it consumes. See this link for a reference: http://technet.microsoft.com/en-us/library/ee748656(v=office.15).aspx
SQL server by DESIGN will always eat up as much ram as you throw at it if you have databases of sufficient size. Have a 32GB database and 32GB of memory ... SQL by default will eat all of it. You can configure SQL to limit the amount of memory it will consume however. Lets say you have 16GB of memory in your system try limiting the SQL buffer to 10GB, that ...
(1) SP will display it as it could not connect to the external data source. Sometimes we setup manual caching mechanisms and as I know, it supports caching by default for Outlook. (2), (3) and (4) When a Business Data column is created, it creates another column associated with it which will be named with a suffix "_ID" to the Business Data Column. You can ...
It seems you are putting a heavy load on the server and that cannot be handled by the SQL Server itself. I would suggest splitting it into chunks, executing one by one and also increase the timeout to something relatively better for the particular query. I think it is ok to increase timeout upto 90 seconds depending on the situation and then can rollback ...
Only top voted, non community-wiki answers of a minimum length are eligible