New answers tagged

2

Installing service packs usually goes like this: detailed step by step guide It shouldn't affect databases, but you may want to test installing SP3 on the test server first. It will help you get an idea how long it takes (management will want to know that beforehand). It will also give you a chance to find out if any of your applications (or anything else) ...


0

I found the issue after a long time. It was due to 1 million+ files in the \MSSQL\log folder. After setting up a job that cleared that folder. The failover after SP install worked fine. The solution was confirmed on both this 2008R2 cluster, and the 2012 cluster we had the same problem on.


0

I found the issue after a long time. It was due to 1 million+ files in the \MSSQL\log folder. After setting up a job that cleared that folder. The failover after SP install worked fine. The solution was confirmed on both this 2012 cluster, and the 2008R2 cluster we had the same problem on


4

Windows Update isn't offering you a Service Pack for SQL Server 2012 to apply to your SQL Server 2014 instance; there is something else on your machine that is triggering it. Could be dozens of things, but most commonly: The SQL Server 2014 instance isn't the only instance on your machine. You may have SQL Express installed (on its own, or as part of ...


2

You can't actually install a service pack for a previous product (2012) onto the current product. I would guess you have SQL Express or some shared components/management studio etc which is what the SP applies to. The easiest way to find out, assuming you aren't inventorying your server any other way would be to run the SP from the GUI and see what it ...



Top 50 recent answers are included