March 6, 2014 at 1:38 pm
I used a free trial of Idera Patch Analyzer on it, which said that it is pre-release and unsupported. My question is, can I tell from this whether this is a legitimate version that was purchased? The person who installed it was very resistant to installing SQL Server 2012 and secretive about the installation. The person was here for a couple of days when I first arrived and left. I don't want to stir up trouble with my new employers by asking these questions if I can find out myself beforehand. There isn't anyone technical to talk about it with. I wanted to prepare for patch installation.
Thanks in advance.
March 6, 2014 at 1:53 pm
I think your best bet is to check out the version in the Build List (check here[/url]) for your version and see if it is before the RTM.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
March 6, 2014 at 3:08 pm
Yeah do SELECT @@VERSION and look in http://sqlserverbuilds.blogspot.com/. Just check if you build that is before the RTM.
--
SQLBuddy
March 7, 2014 at 8:19 am
Thanks Jack Corbett. I see that I have build 10.50.400 level SP2CTP. So it's after RTM. What does it mean that the support status is pre-release and supported is "no"? Does this just mean that it's "de-supported" or past it's lifecycle? I found this page: showing lifecycles for editions of SQL Server.
Can I reasonably conclude that a license was purchased when it was installed recently but that it's past it's lifecycle so there won't be any further patches for it?
Thanks.
March 7, 2014 at 8:20 am
Thanks SQLBuddy123.
March 7, 2014 at 8:58 am
pharmkittie (3/7/2014)
Thanks SQLBuddy123.
CTP is Community Technology Preview. You can install it but it's not the final version and things may be modified before releasing the final version ( RTM). Since you say it's around 10.50.4000, you should be good. 10.50.4000 is SP2. To do further patching, you can either do SP2 CU11 (10.50.4302) or wait for the SP3 release.
--
SQLBuddy
March 7, 2014 at 10:50 am
Thanks again SQLBuddy123.
March 7, 2014 at 11:16 am
You are welcome pharmkittie 🙂
--
SQLBuddy
March 10, 2014 at 7:59 am
SP2 for SQL 2008 R2 went through a CTP stage before it was released. It seems you have got the CTP version of SP2 installed.
If it were my system I would apply the release version of SP2 before applying any further upgrades. This would make sure your system is at the release level expected by any CUs for SP2.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
March 10, 2014 at 4:30 pm
Thanks EdVassie, I appreciate the additional insight.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply