cancel
Showing results for 
Search instead for 
Did you mean: 

SQL Server 2005 SP2 end of mainstream support - Jan 2010

Former Member
0 Kudos

Did not have SP3 on the radar for our project planning and the "end of mainstream support for SP2" has just been brought to my attention.

Been quite content with multiple go-lives on SP2 in June 2008 and then and OS/DB migration from a different DB in May 2009; have not had to perform the application of a new SP in our environment (yet) until now.

Can the SQL Server 2005 veterans shed some light as to your strategies for applying a SP across your landscape?

How much time do you typically wait between the application to DEV and then QA?

How much regression testing do you perform?

Stress / volume testing?

Any other testing?

We are tentatively planning to apply to DEV by late September

QA - apply would be mid October

Regression / volume / stress testing performed mid October to mid November

PRD - apply planned for mid November

Does this approach make sense?

Further suggestions / refinement

Landscape - EP / ECC / BI / PI / Solution Mgr -- all NW 7.0

Thank you in advance

Doreen Anderson

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

Not a "veteran" here - but I wouldn't do too much efforts between servicepacks.

SP3 is out for > 6 months and there are no known big issues (search notes in component BC-DB-MSS and sort by date descending).

If you consider updating and doing regression tests I would also consider switching to SQL Server 2008.

Markus

Answers (1)

Answers (1)

Former Member
0 Kudos

For SQL Server SPs (ECC/BI/CRM...):

How much time do you typically wait between the application to DEV and then QA?

Sandbox (new systemcopy production) - 2 weeks (technical testing done by admins)

DEV - 2 weeks (fuctional testing done by developpers)

QA - 2 to 4 weeks (fuctional testing done by key users)

Thats all. Unfortunately we do not have an automated regression test environment. If you have that in place you could even speed up the process of testing and deploying it.