MSSQL -- upgrade just "Management Studio" ?

OK to upgrade just the server's SQL Management Studio from
2005 to 2008 since I cannot upgrade the PRODUCTION data
because it will break the old ERP system ?
----------------------------------------------------------------
Additional Details:

Doing a "Select @@version" on my SQL server shows that it is
SQL Server 2005 - 9.00.1406.00 (Build 3790: Service Pack 2)
which has SQL Management Studio 2005 software installed.

When I open the "Maintenance Plans, Jobs, etc" via the
server's SQL Management Studio 2005 errors display.

When I open the same via my PC's SQL Management Studio 2008
it works, therefore it looks like a previous developer wrote
some 2008 packages to run on the 2005 server.
finance_teacherAsked:
Who is Participating?
 
lcohanConnect With a Mentor Database AnalystCommented:
Why would you need to install SSMS on that SQL 2005 server box?
If it is mandatory then you can install just the Tools and NOTHING else from the SQL 2008 DVD. You will need to apply SQL 2008 service pack as well but you must be very cautios with what you you are doing. I suggest better Export the packages and try to open/edit them on a client computer that can connect to all servers from taht package connections manager rather then installing SSMS on that server.
0
 
Matt BowlerConnect With a Mentor DB team leadCommented:
I wouldn't upgrade this on the production box. I think if you upgrade the client tools you might also be picking up some of the ODBC drivers and suchlike. V.Risky.
Much better to edit your packages on another machine.
0
 
David ToddConnect With a Mentor Senior DBACommented:
Hi,

I touch 2005 Maintenance Plans from 2008 SSMS all the time and haven't had issues.

However, I did see on SQL 2000 where Maintenance Plans get corrupted, and the only cure is to delete them and recreate them from scratch.

For the standard backup and index maintenance, I'm starting to become a fan of Ola Hallengren's free script you can download from here
http://ola.hallengren.com/

There are about two or three things to change at the top of the script, which you then run.
Jobs are created, which you then have to schedule.

Very robust.

Compared to the maintenance plans, where the file delete/cleanup can occur prior to creating the new backup file, Ola creates and verify's the backup prior to cleanup.

Regards
  David

PS Ola's solution doesn't need tricky things turned on like xp_cmdshell, or clr's - pretty vanilla that just works
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.