Wednesday, September 11, 2013

[MS SQL Server] Is sys.dm_db_index_usage_stats a relatively good indicator of DB useage?

[MS SQL Server] Is sys.dm_db_index_usage_stats a relatively good indicator of DB useage?


Is sys.dm_db_index_usage_stats a relatively good indicator of DB useage?

Posted: 10 Sep 2013 07:27 AM PDT

I'm trying to determine approximately the last time a database was "touched" by users. Thus far, sys.dm_db_index_usage_stats seems to be about the best option. Can't really use the "Last modified" on the MDF / LDF files, as those will change based on SQL accessing them.I'm not trying to use this to determine what indexes might be droppable, just to get an estimate of about the last time a user accessed the DB. The column I'm looking at especially is the last_user_update result.Thanks,Jason

Hot add memory in sql 2008 r2 enterprise

Posted: 10 Sep 2013 05:17 AM PDT

On a single vmware host, we have 8 vm's, each running a single instance of sql server 2008 r2 enterprise (SP2) on Windows 2008 R2. Each VM had 8GB of memory, and we recently hot-added 8 additional GB to each VM. Both the operating system and SQL appeared to recognize the new RAM right away. However, when I increased the SQL min and max memory settings from 4 and 6GB to 8 and 12GB, we started encountering various memory-related errors. The error log was flooded with the following error messages until I set the min and max memory back to 4 and 6GB, respectively:-Memory constraints resulted reduced backup/restore buffer sizes. Proceding with 6 buffers of size 64KB.-Failed to map 16777216 bytes of contiguous memory-There is insufficient system memory in resource pool 'default' to run this query.-Warning: The available page file space has dropped below 4Mb.So my question is, what is the proper procedure for hot-adding memory to SQL servers? Does it require an operating system reboot, SQL service reboot, etc? I was under the impression that "hot-add" meant no reboot necessary, but perhaps that only applies to the guest operating system, and not SQL Server?

No comments:

Post a Comment

Search This Blog