Viewing 15 posts - 1 through 15 (of 279 total)
I ran across http://www.kodyaz.com/articles/create-folder-sql-sys-xp_create_subdir-extended-stored-procedure.aspx and thought it might be helpful for anyone else that may find this page. The Ola Hallengren backup code uses "xp_create_subdir."
May 10, 2017 at 10:38 am
It must be our "specialized" DoD install kit. I found the files just fine on SQL Server 2016 [sic] on my microsoft.com downloaded copy of the install kit.
April 10, 2017 at 2:34 pm
Thanks for the links. You obviously knew what you were looking for. Actually, I googled quite a bit before posting on this forum, but I didn't see anything that was...
October 19, 2015 at 8:44 am
No, I haven't. Can you point me to a link?
October 18, 2015 at 12:44 pm
By the way, we think the reason that the instances would not failback to the original node *without* a reboot of the original node is that the IBM SVC software...
March 26, 2015 at 7:40 am
I think we found the issue.
A while back, I started tracking output from sys.dm_os_sys_memory over time based on code from Glenn Berry (http://www.sqlservercentral.com/blogs/glennberry/2010/08/23/dmv-emergency-queries-from-sql-saturday-_2300_51-in-nashville/).
Despite Microsoft's best efforts, the data we were...
March 26, 2015 at 6:58 am
When I googled the KB's that were installed on 02/24/2015, everyone of them came back with hits on "memory leak."
We're still looking...
March 23, 2015 at 10:43 am
Hmm.... I finally found the syntax to identify the installed patches. There were more patches installed than I thought, but the patches agree between Node B and C. It looks...
March 23, 2015 at 10:33 am
Please see the attached Excel graph of available_page_file_kb from sys.dm_os_sys_memory. We have two scheduled failovers per week to make sure that every node can be patched quickly. This explains the...
March 23, 2015 at 6:57 am
By the way, I tried using "DBCC MEMORYSTATUS," but I'm not having any luck interpreting the output. Even on my laptop, that command generates 700+ lines of output. When I...
March 21, 2015 at 6:46 pm
>>Raising the max server memory on each instance would be a sensible option
Yes, I understand your line of thinking, however, the failures *abruptly* started around 02/25/2015. Prior to that date,...
March 21, 2015 at 6:29 pm
Yes. We are using:
(128 GB - 12 GB) / 9 instances = ~12 GB max memory for each instance
We took this route because we did not want to overcommit RAM...
March 20, 2015 at 5:10 pm
All three nodes are essentially identical blades with 128 GB of RAM. I don't have access to the servers from home, but, as I recall (per Microsoft recommendation), we have...
March 20, 2015 at 12:59 pm
The AWESOME, free Qure tool from DBSophic.com provides some amazing aggregate analysis features. You can't touch that tools capabilities with XEs.
Is DBSophic Qure Profiler still free? I am...
February 5, 2015 at 3:59 pm
Grant Fritchey (2/4/2015)
My book has been updated very extensively for SQL Server 2014.
Grant Fritchey (2/4/2015)
I ran across a copy of your "SQL Server 2012 Query Performance Tuning" book this morning. This looks...
February 4, 2015 at 8:17 am