Viewing 15 posts - 91 through 105 (of 1,523 total)
Has anyone seen any large jump in resource usage after patching? I am very closely monitoring as we roll this out and I am not seeing much change at all...
February 1, 2018 at 11:59 am
Yesterday I also patched two SQL Server 2014s and they had the same messages in the App. server log and the patch was applied successfully. Microsoft needs to change those...
January 24, 2018 at 5:37 am
I applied the 'fix' on a SQL Server 2016. It said successful and everything looks good. However, when I look in the server application log I see these below. When...
January 23, 2018 at 6:19 am
January 2, 2018 at 2:10 pm
December 28, 2017 at 5:54 am
December 27, 2017 at 6:42 am
We use COMMVAULT. It 'seems' quicker and has a very good compression ratio. For doing complete system restores it excels I must say.
December 13, 2017 at 10:44 am
I always create exceptions for .bak and .ldf .mdf .ndf. I also exclude the main SQL Server folders from being scanned. Years ago someone deleted those exceptions and the server was...
December 13, 2017 at 10:42 am
December 11, 2017 at 11:29 am
Today we just upgraded a small system from Win2008R2/SQL 2008R2 to Win2012/SQL 2014. SQL 2014 is the latest version of SQL Server that the vendor has certified.
November 10, 2017 at 12:33 pm
Thank You Yankees for finishing off the Indians... come back from having their backs to the wall and they won 3 straight games.
October 12, 2017 at 5:44 am
October 10, 2017 at 10:24 am
October 3, 2017 at 8:41 am
It will certainly simply patching. I hope vendors take testing CUs more seriously than they do Service Packs now.
October 3, 2017 at 6:02 am
Viewing 15 posts - 91 through 105 (of 1,523 total)