Showing posts with label tools. Show all posts
Showing posts with label tools. Show all posts

Tuesday, March 20, 2012

post SP2 GDR

I have a question about the post SP2 GDR that just came out in the last day or two. My laptop only has the client tools installed, not the server components (except for the SSIS server component). Is there any need for me to install this GDR? Does it impact the Management Studio code which views maintenance plans on remote SQL Servers or anything?

The information about the reason for the update of SQL Server SP2 is contained here:

http://support.microsoft.com/kb/933508/en-us

The basic summary is that if you use SQL Server 2005 Database Maintenance plans (not legacy plans from a migration) which use cleanup intervals, and you have edited those plans with the original SP2 tools, then these intervals may have been "corrupted".

You should install the GDR patch if you have the admin tools, and if you have updated such plans on your server with the original SP2 patch you should, once the GDR is installed, edit those plans and check/correct the cleanup intervals.

|||

Thanks for the reply. I wasn't asking what the patch did, I was wondering whether it was necessary to install on my laptop which only had the management tools and not an instance of SQL Server.

This discussion is unimportant now as Windows Update, just this morning, had me install an 18MB update to fix this very issue.

post SP2 GDR

I have a question about the post SP2 GDR that just came out in the last day or two. My laptop only has the client tools installed, not the server components (except for the SSIS server component). Is there any need for me to install this GDR? Does it impact the Management Studio code which views maintenance plans on remote SQL Servers or anything?

The information about the reason for the update of SQL Server SP2 is contained here:

http://support.microsoft.com/kb/933508/en-us

The basic summary is that if you use SQL Server 2005 Database Maintenance plans (not legacy plans from a migration) which use cleanup intervals, and you have edited those plans with the original SP2 tools, then these intervals may have been "corrupted".

You should install the GDR patch if you have the admin tools, and if you have updated such plans on your server with the original SP2 patch you should, once the GDR is installed, edit those plans and check/correct the cleanup intervals.

|||

Thanks for the reply. I wasn't asking what the patch did, I was wondering whether it was necessary to install on my laptop which only had the management tools and not an instance of SQL Server.

This discussion is unimportant now as Windows Update, just this morning, had me install an 18MB update to fix this very issue.

Monday, February 20, 2012

Ports And Protocols

Hi Folks ,

Got one for you ....

By default what ports and protocols do the following sql tools use...?

Enterprise Manager
SQL Query Analyser
SQL Profiler

And if anybody knows :

Performance Monitor
Mapping drives
Event Viewer
User/Server Manager

Any help would be greatly appreciated ....Do you mean TCP/IP ports and protocols?

Microsoft SQL uses port 1433 for the default instance, and 1434 for named instances. It uses the TDS protocol.

The other tools use a mish-mash of ports and protocols, but I'd start with port 135.

-PatP