Browse by Tags

SQL Server - Have you observed DBCC SHRINKFILE operation performance, on huge databases?
Published 25 April 8 3:30 AM | SSQA.net
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...
SQL Server 2005 TSQL to obtain buffers by object (table, index) in the buffer cache?
Published 1 February 8 6:30 AM | SSQA.net
As a programmer interacting with SQL Server's cache is not often needed, but when you do need to determine what is going on with the cache, or you simply need to flush the execution plans or data pages to tune a query, you now have the means to do...
SQL Server 2005 Enterprise Edition - make data available while creating indexes on large tables!
Published 25 January 8 3:41 AM | SSQA.net
Though it is not a best practice to perform a CREATE INDEX on large tables during the online hours where you have number of users accessing the metadata of SQL Server database. Within SQL Server 2005 Enterprise Edition you can perform ONLINE indexes operation...
Calculate size of an index for a new database?
Published 17 October 7 2:6 PM | SSQA.net
How can you calculate size of an index in a database whenever a capacity planning exercise if performed? By default the size allocated for each user objects depends on the user application and on the amount of space that is created by the application...
Reset cached plan - how to and what to?
Published 14 May 7 3:53 AM | SqlServer-QA.net (SSQA)
I don't believe you would need to reset the cache on a production server, it is not a best practice to perform in this case. Most of the times in development or test environments for the purpose of benchmarking you would need to reset the cache for...
Cached query plans and top stored procedures that are recompiled
Published 11 May 7 6:2 AM | SqlServer-QA.net (SSQA)
We all know that the cached query plans are good to go to attain the performance and no doubt that inefficient query plan will cause more distress to performance with an increased spike in CPU consumption. At the same occurrence of recompilation of a...