SQL Server 2008R2 – How to Uninstall Only SSMS and Profiler

profilersql-server-2008-r2ssms

I'm running SQL Server 2008R2 locally on my dev workstation, and I use SSMS and Profiler quite often. I recently installed the July 2016 version of those tools, and I'd like to remove the 2008R2 versions in order to free-up some disk space.

What is the proper way to remove ONLY those management tools? (I do not want to remove/break my core 2008R2 install)

Best Answer

Go to Programs and Features, select SQL Server 2008 R2, and then the Remove option (people tend to panic that this will just remove everything without further input, but this merely launches a wizard):

After this, you will be guided through a wizard much like installation. On the Select Instance screen, select the "remove shared features only" option:

Then you will get to this screen, where you can select just the management tools:

Though, I don't know why you don't just leave them there. They don't take up an inordinate amount of space, and you never know when you may have to use them (e.g. to manage an SSIS package or maintenance plan from your 2008 R2 instance).

(Also, the astute observer will note that these screen shots all came from different operating systems - I swiped them from the Internet.)

Related Solutions

SQL Server Profiler – How to Download for SQL Server Management Studio

SQL Profiler does not come with SQL Server Express 2008 R2*. You can get it with the installation media for Datacenter, Enterprise, Standard, Web, Developer, or Workgroup licenses.

If you have the installation media, you can get Profiler that way. Otherwise, Developer Edition is available for $50.

There are some other tools available, and you could even create your own server-side traces (for example) without Profiler. Then, use a tool like Qure Workload Analyzer to review the trace files. With 2008 R2, you could in addition use Extended Events to track activity. The advantage is that both of these are less of a performance hit than running Profiler would be.

If you're looking at a point-in-time solution and can install procedures, Adam Machanic's sp_whoisactive could be something to look into.

* Profiler is available in SQL Server 2012 Express Edition SP1 onward. You need to select SSMS (Complete) in the installation options.

Sql-server – Procedure showing different duration / reads in Profiler vs. SSMS

The difference in logical reads leads me to believe that the two executions are getting different plans. This could be because:

there are different set settings between the app that is calling the procedure that profiler is picking up and your instance of SSMS.
you have a different default schema (you really should say exec dbo.SM_SP...).
see this post for more details

You can see if there are two or more different plans for the procedure using something like this, which will also identify if this is caused by either (or both) of the two most likely factors for different plan choice:

SELECT p.plan_handle, p.usecounts, p.size_in_bytes, 
  set_options = MAX(CASE a.attribute WHEN N'set_options' THEN a.value END),
  dflt_schema = MAX(CASE a.attribute WHEN N'user_id'     THEN a.value END)
FROM sys.dm_exec_cached_plans AS p
CROSS APPLY sys.dm_exec_sql_text(p.plan_handle) AS t
CROSS APPLY sys.dm_exec_plan_attributes(p.plan_handle) AS a
WHERE t.objectid = OBJECT_ID(N'dbo.SM_SP_MAILEVENTNAMES')
AND a.attribute IN (N'user_id', N'set_options')
GROUP BY p.plan_handle, p.usecounts, p.size_in_bytes;

Best Answer

Related Solutions

SQL Server Profiler – How to Download for SQL Server Management Studio

Sql-server – Procedure showing different duration / reads in Profiler vs. SSMS

Related Question