SQL SERVER 2012 SP1 on Windows Server 2012 Datacenter Edition. 64 logical CPU 256 GB memory
For any size of table, partitioned or not, a CREATE COLUMNSTORE INDEX statement runs so fast most of the time that I check to make sure it was created. Sometimes, but not all times, when SQL Server is under a significant memory load (CPU load is always trivial) creating a COLUMNSTORE INEX will "lock up" SQL Server and Windows Server to any new connection.
On the occasions when I have a problem (and the same size index may have no problem under what looks like the same conditions) the CREATE INDEX takes hours longer than normal. When it is running I can understand why an overload on memory would cause a timeout for a new connection to SQL Server or for a new query on an existing connection but I don't understand why this would affect connections to Windows. I cannot get an RDP connection to Windows. I cannot open Perfmon. If I go to another server it takes many minutes to connect with RDP Manager. PowerShell connections time out. The DAC times out.
I have read about upping the Memory Granted to the default Workload Group in RG. I haven't added any cumulative updates.
Any ideas on why new connections to Windows time out? Is the COLUMNSTORE INDEX create using Windows memory. Windows has more GB of memory than it requires.
carpe cras