Hot answers tagged

4

Well one thing you may want to consider doing is validating your application(s) still work on a test instance that contains the same database and upgrading it to the newer service pack. While rare and usually changes are backward compatible, there could be behavior changes to things like the optimizer that would be impossible to guess exactly how they might ...


4

This happens because the msdb log file name has been changed from the default which is "MSDBLog". In my case, it was called "msdb_log". The name "MSDBLog" is hard-coded into the upgrade script so it fails if the name has been changed. To fix the problem, we need to rename the log file to 'MSDBLog'. We have to start SQL with trace flag 902 to stop it from ...


4

It looks like you are already at Service Pack 1 (this is why MSSQLSERVER is checked and greyed out). 11.0.3000 and 11.1.3000 are essentially the same thing, different files just have different reasons for exposing a different number in the middle - that number is really not relevant to your problem. So now you just need to download and install the latest ...


4

Cumulative updates are exactly that, cumulative. CU2 for example contains all of the fixes included in CU1. As such, the only SP or CU that matters is the last one to be applied which you can determine with: SELECT @@VERSION and Google or a reference list of SQL Server versions. SQLServerBuilds is the popular unofficial list, KB321185 is the official ...


4

Microsoft recommends you update to both the latest SP and the latest CU which means SP3 and CU2. As a side note if you used WSUS with the right classifications ticked this is how it would be updated "automatically". I wouldn't recommend this but it does help when explaining your update policy to users. For future versions you can also check ...


3

You are running SQL Server build 9.00.5294.00 that is more current than SP4 which is 9.00.5000. Your server has already been updated. (http://sqlserverbuilds.blogspot.com/) (Build 7601: Service Pack 1) is the version of the operating system.


3

You should be able to apply the SP3 without dropping any merge replication publications. The order of upgrade should be to upgrade (1) distributor, then (2) publisher, then (3) subscribers. The SP3 is for SQL Server 2008, not the SQL CE 3.5 mobile tools. Since you are running merge replication then I assume that you have SQL CE 3.5 SP2. So all should be ...


2

I think this is a pitfall. I recall SQL 2005 and older versions requires active nodes to be updated. SQL 2008 and later versions allow passive node updates like the walkthrough you described. A posting from Linchi Shea explains it well.


2

You shouldn't have any issues, just be sure that when you plan your maintenance for SQL Server you don't get blocked by the "Restart Computer" rule. E.g. if you have installed Windows Updates in the meantime you might not know that Windows needs to be restarted until you enter your maintenance window... For some background, I got surprised by this during a ...


2

The logs led us to review our Cluster services: There was an error to lookup cluster resources. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 4104. Description: . HResult : 0x86d80014 FacilityCode : 1752 (6d8) ErrorCode : 20 (0014) Data: errorMessage = There was a failure to call ...


2

For the latest CU and builds (this article will also include service packs when released): SQL Server 2014 build versions As of 2015-01-13, SQL Server 2014 is currently on CU5, which was released Dec. 17, 2014. Service pack 1 has not yet been released. Another similar article, specific to Service Packs: How to obtain the latest service pack for SQL ...


2

I would always err on the side of just installing the service pack again (it will know which components, if any, to update). Especially when adding client tools to a workstation - where this is not a major disruption. (And if you're adding BIDS to a production server, you should reconsider IMHO.)


2

Edit: I reviewed this a bit further and another cause of this issue has been the Windows Installer cache. That seems to create a 'file not found' error when looking for the copy of the msi/msp package that's copied into the Windows directory with the update GUID. We're not seeing that here, but I think it's because we're not seeing the actual log file for ...


2

From the error messages in the summary log, it seems like the baseline MSIs could not be found (perhaps because you cleaned out C:\Windows\Installer?). I would suggest: Installing the QFE instead of the GDR (this will attempt to patch you to 10.0.6535, giving you this security fix and a couple of other fixes described here). Not using Windows Update, but ...


1

I saw a SQL update in Windows Update pulled from our WSUS server, Security update for SQL Server 2008 R2 Service Pack 3 and not realizing that it's an cumulative update, it managed to update the SQL server to 10.50.6220 (SP3 = 10.50.6000) without any error. I'm guessing probably some issue with the original SP3 setup. I'll update here again if I face any ...


1

It seems there is an open issue like this, in Microsoft Connect that may have been resolved on 2008 in later updates. maybe that is the reason.


1

You need the express service pack from here: https://support.microsoft.com/en-us/kb/3072779


1

As TheGameiswar has mentioned, the upgrade adviser is incredibly helpful for pointing out issues that can arise with the upgrade. However, it will only check for things IN the database. So if you have ad-hoc queries being ran, or worse yet sql files scattered all over the place, those will not be tested. When I upgraded our SQL 2000 servers to 2014, we had ...


1

I'm not 100% certain if you are asking for advice on your upgrade to SQL 2014, or if you are worried about applying a CU to your SQL 2014 SP1 instance. Let's assume you are asking about the latter. Here's what you need to consider when it comes to SQL Server patching. This applies to all Microsoft patches - SQL SPs and CUs and Windows OS patches: You've ...


1

Like @billinkc, I use sqlserverbuilds.blogspot.com as my go-to list when I see a build I'm not familiar with, and to check before each update cycle. Note that there's also build 12.00.2464 after CU5, "3024815 Large query compilation waits on RESOURCE_SEMAPHORE_QUERY_COMPILE in SQL Server 2014"


1

As per logs you posted Products Detected Language Level Patch Level Platform Edition Database Services (ALCSQLMFG) ENU SP1 2005.090.2047.00 x64 STANDARD Database Services (MSSQLSERVER) ENU SP4 2005.090.5069.00 x86 STANDARD Reporting Services (MSSQLSERVER) ENU ...


1

Consider this as answer SP3 is new and thoroughly tested its highly unlikely it would create any issue but again I would recommend you not to proceed without any testing and that too when Cluster is involved. Also asking whether anybody faced issue will lead you in problem, what if somebody writes 'Yes I have done and its working fine' yes they are correct ...


1

In addition to the sqlserverbuilds.blogspot.com and Microsoft pages mentioned earlier, I also like sqlserverupdates.com created by Brent Ozar et al.


1

Almost every time I've had an SP installation issue on a stand-alone server, it was because the resource database was moved or it was not in the same directory as the master database. Many articles I'm finding correlate your error to this exact conclusion including this one. I would start there and if you find it to be the case, move the system databases ...


1

From BOL For merge replication, a Subscriber to a merge publication can be any version no later than the Publisher version. This means, you have to patch Publisher first and then Subscriber to be 100% sure that you wont be encountering any issues.



Only top voted, non community-wiki answers of a minimum length are eligible