- MICROSOFT SQL SERVER 2012 EXPRESS SP2 INSTALL
- MICROSOFT SQL SERVER 2012 EXPRESS SP2 UPDATE
- MICROSOFT SQL SERVER 2012 EXPRESS SP2 UPGRADE
That sounds pretty compelling, right?ĭon’t get too comfortable, there’s even more to consider. This CU1 has some pretty critical sounding fixes in it, including out of memory errors, incorrect results on parallel queries, and databases offline if an index rebuild is performed when the transaction log is full.
MICROSOFT SQL SERVER 2012 EXPRESS SP2 UPDATE
I subscribe to this by RSS, and anytime I need to do research on cumulative updates, I head to their blog and use their posts to find all the related links for documentation.įor SQL Server 2012, you’ll find that Cumulative Update 1 has been released post SP1, so you can consider the version SQL Server 2012 SP1 CU1.
My favorite resources for cumulative updates is the SQL Server Release Services Blog. However, there are many people who prefer to test and go live on their chosen version of SQL Server + Latest Service Pack + Latest Cumulative Update– because these updates do fix some doozies.
MICROSOFT SQL SERVER 2012 EXPRESS SP2 INSTALL
These updates are more frequent than service packs, and technically Microsoft recommends that you only install them if you are impacted in an issue that the Cumulative Update corrects. You also need to consider the Cumulative Updates that Microsoft releases for SQL Server.
You’ve found your service pack, so you’re good, right? Not so fast. Cumulative Updates Upgrading ain’t easy, but sometimes it’s REALLY worth it If you have any of these doubts, read the list of bugs the Service Pack fixes- but note that you’ll also have to read the release notes for all the cumulative update packages it includes as well. If you forgot to install the service pack at the beginning of testing, you may wonder if it’s worth it to go back and install the service pack and re-test. Sometimes new features get snuck into Service Packs these days - check out what features were added in SQL Server 2012 SP1. But like everything else, they may contain something that has unexpected side effects– so you need to test your application with the service pack before you change it in production. Service Packs contain important fixes for a product and are tested even more rigorously than incremental releases like cumulative updates, so they’re pretty important to install. SQL Server 2012 Service Pack 1 was released in November 2012. Identify SQL Server Service Packsįirst, check if a service pack is avaiable for your version of SQL Server, and which one is the latest. SELECT decode your version number, check out this big list of SQL Server Builds. You can find your current SQL Server version by going into your Server Properties in Management studio, or running the TSQL command: Over time, lots of fixes are released for each version: Service Packs, Cumulative Updates, and hotfixes. When a new SQL Server version is released you get the “RTM” version of the product. The SQL Server “version” is often called the “patch level” of SQL Server. But which version of SQL Server do you choose? What’s the SQL Server Version? I turned my SQL Server Version up to 11 …. You need to make sure that all testing goes against the same version of SQL Server you’re going to go live with. Suddenly you realize you’re not quite ready. You’re ready to install developer edition in the test environment.
You’ve sized new hardware in production and sketched out your migration plan. You’ve selected your SQL Server Edition and worked out your licensing agreement.
MICROSOFT SQL SERVER 2012 EXPRESS SP2 UPGRADE
It’s finally time– you’ve been given the thumbs up to upgrade to SQL Server 2012.