In general it is not a best practice to perform SHRINK database operation on a production server, atleast regularly! Sometimes it may be compulsory to keep them sized in order to ensure the disk storage is not compromised for any sudden changes to databases ETL processes, coming to the point by design...
What kind of performance issues you see on day-to-day basis within your environment? The following elements are important factors that can add fuel to the fire (problem): Faulty hardware • Hardware that is not configured correctly • Firmware settings • Filter drivers • Compression • Bugs • Other conditions...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-17-2008
Filed under: sql server, memory, analysis, disk, IO, monitoring, configuration, iometer, contention, latches, latching
This is a very tricky question and hard to stick to 1 or few solutions as answer, it depends! Overall the say is if there isn’t any resource contention (from your pre-installation testing & analysis) and there is enough of each resource to go around, then there is usually no reason to set any restrictions...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-04-2008
Filed under: sql server, memory, maintenance plan, i/o, clustered, best practice, monitoring, resources, configuration, performance monitoring, contention
Memory - an important aspect of system performance within a RDBMS platform, not specific to a database product or application. Coming to Microsoft related products such as Windows Server and SQL Server so on, various resources available on web such as MSDN blogs, Books Online and articles, frequently...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-01-2008
Filed under: sql server, performance, memory, cache, disk space, troubleshoot, system, best practice, raid, hardware, monitoring, configuration, baseline
Have you seen the above message within the SQL Server error logs? If not then no need to worry and make sure to continue your performance monitoring tasks. So when to be concerned! It is evident that SQL Server 2005 component handles memory differently as compared to SQL Server 2000 version. As one of...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
03-07-2008
Filed under: sql server, performance, memory, dmv, windows, 2000, 2005, awe, 64 bit, monitoring, worker threads, paging out, buffers, verison