Re: Cannot find a GUI to execute a query

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thank you. I'll give that a try.

Kelly.

"Ekrem Önsoy" wrote:

For now, I don't have a chance to try but I can suggest you to try
installing SSMSE 2008. I believe it works side by side SSMS 2005 because
SSMS 2005 and 2008 works side by side (which was not possible before CTP 6 I
guess). So you'll not have to uninstall Client Tools for 2005 version and
you'll still have SSMSE 2008. How about this?

--
Ekrem Önsoy


"KellyP" <KellyP@xxxxxxxxxxxxxxxxxxxxxxxxx>, iletisinde şunu yazdı,
news:6565AD9A-8342-4059-A4C1-5D3336BAA39E@xxxxxxxxxxxxxxxx
Hi Ekrem,

Thanks for getting back to me so quick. I had thought of reverting back
to
SSMSE but there are some other features, like SQL Server Profiler, that I
would then need to give up. Six of one hand.....

I guess I can still 'Script Stored Procedure As Execute To' a new window,
set the parameters manually and get the same results. GUI interface would
have been nice though....

Thanks again for your help.

Kelly.

"Ekrem Önsoy" wrote:

Hello Kelly,

How about using SSMSE instead of SSMS (2005)?

You probably know that SSMSE is a limited version of SSMS, however it can
do
the thing you are looking for.

--
Ekrem Önsoy


"KellyP" <KellyP@xxxxxxxxxxxxxxxxxxxxxxxxx>, iletisinde şunu yazdı,
news:0CDF96C2-D7B5-409F-A6B1-EB541D10B86E@xxxxxxxxxxxxxxxx
Hi Ekrem,

You nailed what happened exactly. Unfortunately, moving to SSME 2008
where
I work is not going to happen anytime soon. Do you know any way to get
around the problem?

"Ekrem Önsoy" wrote:

I exactly know what's going on with your system... (too much arrogance
here?)

Let me tell you about your scenario:
You, had SQL Server Management Studio Express (2005) installed on your
PC
before and now you have SSMS (2005). As SSMS and SSMSE can't work
together
on the same system, SSMSE was removed to install SSMS.

When you connect to a SQL Server Express Edition instance using SSMS
(2005
only, but you'll see the option with SSMS 2008), you won't see
"Execute
Stored Procedure..." item on the popup menu as you complain, however
if
you
used SSMSE 2005 (which you probably used to use before) then you'll
see
this
option and it does not matter even if you are connected to a SQL
Server
Express Edition instance or another edition.

I performed this test using a VM, SQL Server 2005 Std Edition and
Express
Edition on Windows Server 2003. RTM version of SSMS (2005) behaves the
same
as the lastest version.

--
Ekrem Önsoy


"KellyP" <KellyP@xxxxxxxxxxxxxxxxxxxxxxxxx>, iletisinde şunu yazdı,
news:36CD8E64-D4B3-4BD5-9AE2-755A17E758EC@xxxxxxxxxxxxxxxx
Erland,
Thanks for responding. I am using SSMS 2005 and as far as I can
tell I
do
have execute permissions. . Here is the version info:

Microsoft SQL Server Management Studio 9.00.4035.00
Microsoft Analysis Services Client Tools 2005.090.4035.00
Microsoft Data Access Components (MDAC) 2000.085.1132.00
(xpsp.080413-0852)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.13
Microsoft .NET Framework 2.0.50727.1433
Operating System 5.1.2600

FYI, the "Execute Stored Procedure" item used to be there until one
day
our
helpdesk removed SQL 2005 express from my desktop and loaded the
SSMS
2005
client piece on my desktop. I then loaded the express db back to my
PC
so
I
could have a local db. Since then the "Execute Stored Procedure"
item
no
longer shows up on when using the express db but does show up on all
the
other dbs.

"Erland Sommarskog" wrote:

KellyP (KellyP@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
No. I am talking about the "Execute Stored Procedure" item on
the
context menu that shows up if you right click on a stored
procedure.
The context menu item is there if I right click on a SP in a 2005
database but not there if I right click on a SP in a SQLExpress
2005
database.

Exactly which version of SQL Server Management Studio are you
using?
I connect with SSMS 2008 to both SQL 2008 and SQL 2005 Express
instances,
and the item is there on the context menu.

The only thing I can think of is that you don't have EXECUTE
permission
on the procedure and SSMS is smart enough to check for this.

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx





.

Relevant Pages

  • Re: Cannot find a GUI to execute a query
    ... So you'll not have to uninstall Client Tools for 2005 version and you'll still have SSMSE 2008. ... SSMSE but there are some other features, like SQL Server Profiler, that I ... I guess I can still 'Script Stored Procedure As Execute To' a new window, ... How about using SSMSE instead of SSMS? ...
    (microsoft.public.sqlserver.tools)
  • Re: Cannot find a GUI to execute a query
    ... You probably know that SSMSE is a limited version of SSMS, however it can do the thing you are looking for. ... had SQL Server Management Studio Express installed on your PC ... > Microsoft Analysis Services Client Tools 2005.090.4035.00 ...
    (microsoft.public.sqlserver.tools)
  • Re: Cannot find a GUI to execute a query
    ... How about using SSMSE instead of SSMS? ... had SQL Server Management Studio Express installed on your PC ... > Microsoft Analysis Services Client Tools 2005.090.4035.00 ...
    (microsoft.public.sqlserver.tools)
  • Re: SSIS - can SSIS pkg recognize a drive letter within SMS job?
    ... Realized from your process description that you were running SSMS from your ... I normally run SSMS on our Sql Server using a remote (terminal ... Uploaded the SSIS package which was simple and just contained one ... What is your SQL Server Agent service account? ...
    (microsoft.public.sqlserver.dts)
  • Re: Cannot find a GUI to execute a query
    ... SSMSE but there are some other features, like SQL Server Profiler, that I ... I guess I can still 'Script Stored Procedure As Execute To' a new window, ... How about using SSMSE instead of SSMS? ...
    (microsoft.public.sqlserver.tools)