March 4, 2011 at 12:38 pm
I know this has been discussed a number of times in the past and I have read most of the topics on this forum about it, sorry for the repost about it.
Our product is currently running on 2005 and 2008 but have no customers on 2008 R2 yet. We require a fix that is bundled with the latest service pack for each of these versions but is not part of R2 yet. I can recommend that new customers not use R2 but I am worried that 2008 is taking a back seat to 2008 R2. Is there any harm by requiring they not use R2? Should I be worried about availability and support?
March 4, 2011 at 1:39 pm
2008 and 2008 R2 have the same support end dates, so support shouldn't be a problem. But for example in our shop we now only have 2008 R2 on our servers, so if you said your product wouldn't run on 2008 R2 we would just eliminate it as a choice and look for something else.
Is the bug a major issue for your product? Has Microsoft said when the fix for it will make it into a 2008 R2 CU or SP?
March 4, 2011 at 1:55 pm
Thanks for the response.
The bug has been fixed in a 2008 R2 CU but I was unable to location a SP for R2 yet or if there was even one in the works. I don't think we want to run CU's in production.
Our product up until a year or so ago require only 2005. Do to the nature of the product, I would not see 2008 vs 2008 R2 as a reason to look for another product.
We can strongly recommend using 2008 over 2008 R2, I just don't want to get them into a position where the direction we told them to go ends up being the wrong one.
March 4, 2011 at 2:17 pm
If you go by this you will not see a service pack for SQL 2008 R2 until 12-months from the RTM release.
Which it was released in May 2010 so they should have a service pack in the works that will probably have a CTP release in the coming months.
I don't understand why you would not run a CU in production. The service packs for the most part are just all the CUs from the RTM or previous SP roled up into one.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
March 4, 2011 at 2:24 pm
We are currently running 2008 R2 CU5 in production (and we are about to evaluate CU6 on the dev server.)
In our case if we didn't put CUs in production we would have to wait for the SP, since there are a number of issues that we ran into that were resolved with CUs.
Rather than say you don't support 2008 R2 yet, I would say that you support 2008 R2 CUx. Same would go for 2005/2008, make sure you specify what SP/CU combination has the fixes that your product requires. Doing that lets you prospective clients make an informed decision about which version they want to run your product on.
March 4, 2011 at 3:12 pm
Thanks guys. I thought I read that CU's weren't meant for production. I will take a look at the latest CU on my system here. Our next scheduled release isn't until summer so it sounds like a SP might be available by then anyways.
March 4, 2011 at 3:17 pm
CUs aren't meant for installation just because they are released, Microsoft says to only install them if they are supposed to resolve an issue you are experiencing, but I think a number of places install them as a matter of course now to get in front of the issues.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply