ExecuteRow - Missing Definition

Hello,

I'm using Visual Studio 2005 with ADO.Net 2.0 but I am missing a definition for the sqlcommands' object "ExecuteRow"

oCommand =new System.Data.SqlClient.SqlCommand();

oCommand.ExecuteRow() ---------> this is the missing definition

Any ideas anyone ?

The SqlCommand class has no ExecuteRow method. Seethis thread.

What are you trying to do?

Don

|||

well I'm actually just running some tests (I'm currently migrating from 1.1 to 2.0)

I have a book by WROX which specifies the definitions for the command object (See attached image), it contains

a definition for ExecuteRow

|||

ItayZ:

I have a book by WROX which specifies the definitions for the command object (See attached image), it contains

a definition for ExecuteRow

Looks like you need a better book. ExecuteRow was dropped between Beta 1 and Beta 2.

|||

Geez, I hate day and date books. They inevitably have stuff wrong, since they have to go to press months before the final release. And I'm afraid that I've written a few. But Never Again.

A better book is indeed in order, but in the meantime you might check the Wrox Web site for an errata sheet.

Don

Execute Stored Procedure option missing from Object Explorer

The option when you right click on a stored procedure to Execute where
it then pops up a nice helper dialog to fill out the parameters is
missing in my SQL Server Management Studio console. The funny thing is
that it was there at one time when I had upgraded from MSDE to SQL
Server Express and installed the SSMS Express. When I got a hold of
and installed the full version of the studio tools on top of that,
stuff was not working correctly like diagrams and books online. So I
uninstalled everything and then reinstalled SQL Server Express and SQL
Server Tools from the SQL Server 2005 Developer Edition DVD. Now that
nice feature is missing from SMSS. Does anyone know how I can get that
option back?Hi Mark
On my RTM version of SQL Server 2005 (Developer Edition) there is an
"Execute Stored Procedure..." option when you right click the procedure whic
h
will allow you to do this, there is also the "EXECUTE to.." option on the
"Script Stored Procedure as" menu. I am not sure what is available in
Microsoft SQL Server Management Studio Express.
John
"Mark" wrote:

> The option when you right click on a stored procedure to Execute where
> it then pops up a nice helper dialog to fill out the parameters is
> missing in my SQL Server Management Studio console. The funny thing is
> that it was there at one time when I had upgraded from MSDE to SQL
> Server Express and installed the SSMS Express. When I got a hold of
> and installed the full version of the studio tools on top of that,
> stuff was not working correctly like diagrams and books online. So I
> uninstalled everything and then reinstalled SQL Server Express and SQL
> Server Tools from the SQL Server 2005 Developer Edition DVD. Now that
> nice feature is missing from SMSS. Does anyone know how I can get that
> option back?
>|||Thanks for the reply. I have the RTM version of SQL Server 2005
Developer Edition installed (just the tools, not the engine). You have
the open "Execute Stored Procedure..." and its missing on my
installation and we have the same version installed. Anyone know how
to get the option back?|||I just noticed something. I was connected to a SQL Server 2000
instance and I noticed that the option "Execute Stored Procedure.." was
available when I right clicked on a stored procedure. So I opened a
connection to my local SQL Server 2005 Express instance and the option
is not there. There must be something different in the configuration
of the database that I cannot see.|||Hi
The databases I used were upgrade from SQL 2000. Have you check that your
are granted execute permission to this procedure?
John
"Mark" wrote:

> I just noticed something. I was connected to a SQL Server 2000
> instance and I noticed that the option "Execute Stored Procedure.." was
> available when I right clicked on a stored procedure. So I opened a
> connection to my local SQL Server 2005 Express instance and the option
> is not there. There must be something different in the configuration
> of the database that I cannot see.
>|||This is happening on all my stored procedures. I am logged on using
Windows authentication and I am an administrator. And I can execute it
by writing a query or using the Script Stored Procedure As... EXECUTE
to. But for grins, I granted explicit permissions for me to execute a
stored procedure. It did not work. Thanks for the suggestion.
Anyone else?|||Hi
The only other suggestion I can think of is to try a fresh install on a
different machine.
John
"Mark" wrote:

> This is happening on all my stored procedures. I am logged on using
> Windows authentication and I am an administrator. And I can execute it
> by writing a query or using the Script Stored Procedure As... EXECUTE
> to. But for grins, I granted explicit permissions for me to execute a
> stored procedure. It did not work. Thanks for the suggestion.
> Anyone else?
>|||Mark (mark@.staffordcastle.com) writes:
> This is happening on all my stored procedures. I am logged on using
> Windows authentication and I am an administrator. And I can execute it
> by writing a query or using the Script Stored Procedure As... EXECUTE
> to. But for grins, I granted explicit permissions for me to execute a
> stored procedure. It did not work. Thanks for the suggestion.
> Anyone else?
Unfortunately, this sounds completely strange to me. Particularly when you
say that you see EXECUTE when you connect to an SQL 2000 Server. It is as
if Mgmt Studio had a per-server configuration for what is to be in the
menus. But I have never heard of such a setting.
I suggest that you log a bug at
http://lab.msdn.microsoft.com/ProductFeedback/. It is not likely that
it will lead to anything, as I guess that you are not able to produce
a reproducible scenario. (Yes, it's reproducible on your machine, but
your machine is not in Redmond.) But maybe if you are lucky, someone
knows about the secret switch.
If possible, it would be interesting to hear what happens if you connect
to a second SQL 2005 instance.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

execute package task

I am missing something simple that's killing me.

I am trying to execute a child ssis package using the execute package task. I add execute package task to the parent package and in the package task editor, under the package options I choose: filesystem for location, I choose new connection and create a connection to the package on the filesystem I want to execute, packagenamereadonly is blank. I execute the parent package and get an error that I did not specify the name of the package in the execute package task object. Now, since I can't populate the package name, as that option is readonly, I am not sure how to remove my headache. Anyone see what I'm doing wrong? None of these packages have security.

-Aaron

Ok, nevermind.

The error was actually in my child package. The child SSIS package was running a DTS 2000 package via the execute DTS2000 package task. The DTS 2000 package was loaded internally and for some reason there was a corruption somewhere in that task. When I deleted the task and reloaded the DTS 2000 package the problem was resolved.

Execute Mutiple Tasks In Debug Mode

Maybe I'm missing something, but I can't find how to run multiple tasks in sequence while in Visual Studio debug mode. In DTS design mode I grew accustomed to right-clicking tasks one-at-a time, but in SSIS I find the additional step of having to exit Debugging mode after every task gets old after a while.

There must be a way to start execution at a certain task and have the package continue all the way to some other specified task. It would also be nice to have every task in a Group execute in sequence and stop (even if connections continue beyond the group). I could even settle for repeatedly clicking the Continue button in Debug mode, but it's always grayed out when the current task is finished!

Can this be achieved by setting breakpoints?

I have previously requested "Execute from here" functionality in the control flow. You can vote for this request here: http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=a2548612-b602-42ab-9ff9-563d927674f8

Adding a comment would help as well.

In the meantime, you can place all required tasks into a sequence container, right click on the sequence container and select "Execute task". All tasks in the container will be executed.

-Jamie

|||

Sequence container appears to be what I was looking for. Thanks. It seems obvious now that you've pointed it out, but features are easy to miss with so much new functionality.

I added some comments on your request.