SQL Server 2005 64 bit install on Server 2003 64 bit server, issue with SSMS

Installed SQL Server 2005 64 EE. Correct in that it installs 32 bit version of SSMS? If I installed the 64 bit Service Pack 3, but the version of SSMS still shows as 9.00.1399 which is RTM. DO I need to run the SP3 32 bit install in order to patch SSMS? Then if SSMS is not patched can this cause issue with managing database engine?

more ▼

asked Mar 05, 2010 at 03:02 PM in Default

Shawn_Melton gravatar image

5.4k 20 21 29

(comments are locked)
10|1200 characters needed characters left

1 answer: sort voted first

Yes. You are correct in saying that it installs the 32 bit version of SSMS. It does that regardless.

My memory is failing me, but something happened in our environment when I skipped SP2 and went directly to SP3 so I've been applying SP2 first and then SP3 just so that I don't have it happen again. Wish I could remember what "IT" was.

As far as the 9.00.1399 version, it sounds like you've already installed the x64 SP3 and you are having issues. Have a look at this discussion.

Are you using the client tools on the server or on your desktop? If it's your desktop, have you patched your local machine as well?

You can also look at: http://www.sqlservercentral.com/Forums/Topic464159-146-1.aspx http://sqlblog.com/blogs/aaron_bertrand/archive/2009/08/21/how-to-really-detect-the-version-of-ssms-you-are-running.aspx which leads you to some helpful info on finding SSMS versions and managing different database engines here.

more ▼

answered Mar 06, 2010 at 04:32 PM

Jason Crider gravatar image

Jason Crider
453 10 10 12

Thanks...the maintenance plan issue is with adding objects to them and the wizard does not run (not that I use them, other co-workers do). I found that issue to be the 32-bit DLL files get unregistered when you install the 64-bit patches (which the KB was for SP2 but I assume the same is true with SP3). It has the command to re-register the 32-bit DLL files.

The other issue I have is when I create a SQL Agent job to say do a clean-up of files, and then backup of certain databases I cannot make changes to it. Meaning I go bring the properties window back up, but nothing is there (the name of the job disappears, steps, and schedules are not present). I can query the msdb.sys.sysjobs, jobsteps, etc and the job exist, I just can't change anything in the GUI. Nothing in the logs is indicating why this is.

We are scheduled to patch the server this week so I asked the technician that is going to do it to run the 32-bit SP3 install against the server, that should patch SSMS. SSMS is running from the server not from our desktop (multiple environments we support don't allow us to run from desktop to connect to every server).

Mar 07, 2010 at 09:13 AM Shawn_Melton
(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: Mar 05, 2010 at 03:02 PM

Seen: 1491 times

Last Updated: Mar 05, 2010 at 03:13 PM