August 24, 2009 at 10:07 am
Good afternoon,
I've found some information through browsing the net but not all in regards to the service packs for SQL Server Management Studio, some details are appearing to still be hazy for me.
Does SSMS have separate service packs & updates to the other components of SQL2005? Or is it included in cumulative updates for the SQL 2005 database engine?
My current version of SSMS on 'Help-->About' is: Microsoft SQL Server Management Studio 9.00.1399.00 (which I thought is release?)
And the database engine version is: Microsoft SQL Server 2005 - 9.00.3077.00 (X64) Dec 17 2008 20:40:08 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.0 (Build 6001: Service Pack 1). Yes I know that service pack 3 has been out for a while now, but am still new to this job and haven't applied the SP to this server yet 🙂
I'm currently finding with this version of SSMS that when I attempt to access the properties of SQL server agent jobs they are all blank. I've read through varying sources that a service pack needs to be applied to resolve this. Can anbody point me in the right direction in regards to SSMS's service packs? The install disc has only SP1 software.
Thanks in advance,
Dan
August 24, 2009 at 10:16 am
See the service packs are commulative for SQL Server as a whole.
Try to run the following commands on your SQL Server and see what comes.
exec sp_server_info
go
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
August 24, 2009 at 10:21 am
Danb7183 (8/24/2009)
when I attempt to access the properties of SQL server agent jobs they are all blank. I've read through varying sources that a service pack needs to be applied to resolve this.
There can be n number of reasons for this.
what i think is you should first connect to the server with sa or systemadmin role and then try exploring the SQL Server Agent sub-heads.
Upgrade this to minimum SP1, this has also worked on one of my site.
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
August 24, 2009 at 10:23 am
Sarab (8/24/2009)
See the service packs are commulative for SQL Server as a whole.Try to run the following commands on your SQL Server and see what comes.
exec sp_server_info
go
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
Ok thanks Sarab.
The results from the above system stored procedure (apologies on lack of formatting):
1DBMS_NAMEMicrosoft SQL Server
2DBMS_VERMicrosoft SQL Server Yukon - 9.00.3042
10OWNER_TERMowner
11TABLE_TERMtable
12MAX_OWNER_NAME_LENGTH128
13TABLE_LENGTH128
14MAX_QUAL_LENGTH128
15COLUMN_LENGTH128
16IDENTIFIER_CASESENSITIVE
17TX_ISOLATION2
18COLLATION_SEQcharset=iso_1 collation=Latin1_General_CI_AS
19SAVEPOINT_SUPPORTY
20MULTI_RESULT_SETSY
22ACCESSIBLE_TABLESY
100USERID_LENGTH128
101QUALIFIER_TERMdatabase
102NAMED_TRANSACTIONSY
103SPROC_AS_LANGUAGEY
104ACCESSIBLE_SPROCY
105MAX_INDEX_COLS16
106RENAME_TABLEY
107RENAME_COLUMNY
108DROP_COLUMNY
109INCREASE_COLUMN_LENGTHY
110DDL_IN_TRANSACTIONY
111DESCENDING_INDEXESY
112SP_RENAMEY
113REMOTE_SPROCY
500SYS_SPROC_VERSION9.00.3042
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition'):
9.00.3042.00SP2Developer Edition
Is this not just returning the details for the server and not SSMS?
Thanks,
Dan
August 24, 2009 at 10:33 am
As already stated SQL Server gives commulative Service Packs , SSMS is just a Client tool for SQL Server.
This can happen only if you are using SSMS of a different machine and trying to connect to some other SQL Server and then comparing the both.
Tell me if this is what you are doing?
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
August 24, 2009 at 10:48 am
Yes, it is what i'm doing.
I didn't quite understand what you said in your first post, but now fully understand.
I've just updated the client tools on my local machine and the SQL Agent jobs are now no longer empty 😀
So, issue resolved.
Thanks for the info Sarab,
Dan
August 24, 2009 at 11:00 am
Happy to help you 🙂
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply