Debugging into SqlCommand.ExecuteReader

[BuddyWork]

Does anyone know if there are any articles explaining how
I could debug into SqlCommand.ExecuteReader so I can see
why I am getting a particular error.

thanks

[Vadym Stetsyak]

What error are you getting?

"BuddyWork" <an*******@discussions.microsoft.com> wrote in message
news:22****************************@phx.gbl...

Does anyone know if there are any articles explaining how
I could debug into SqlCommand.ExecuteReader so I can see
why I am getting a particular error.

thanks

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

I don;t think that it's possible, as you don;t have the source code for it
or its being compiled with debug info the only way is to debug the IL code
:)
Anyway, I don't really think that it's necessary, I would suggest you to
post the problem you have and maybe it's possible to help you without need
to decompile ExecuteReader() :)

Cheeers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"BuddyWork" <an*******@discussions.microsoft.com> wrote in message
news:22****************************@phx.gbl...

Does anyone know if there are any articles explaining how
I could debug into SqlCommand.ExecuteReader so I can see
why I am getting a particular error.

thanks

[BuddyWork]

Hello,

The problem is that when using SqlCommand.ExecuteReader
and the SQL statement raises an error of severity of 16
then ExecuteReader throws an exception, when you use
OdbcCommand.ExecuteReader the exception is not raised but
when you call Read() method of the OdbcDataReader you then
get the exception which is correct, basically SqlClient
does not let you call the Read method, the main problem is
that if run a Sql statement of say
'Need to create the following SP first.
create proc test
as
rollback tran
go

now run the following SQL through SqlCommand and then
OdbcCommand
begin tran
execute test
select hello="World"

you will notice that SqlCommand throws an exception on
ExecuteReader function where OdbcCommand does not, so Odbc
allows you to call Read and NextResult to go through the
recordset and retrieve your data, wher SqlClient does not
because you don't get the SqlDataReader object back.

Thanks,

-----Original Message-----
Hi,

I don;t think that it's possible, as you don;t have the source code for itor its being compiled with debug info the only way is to debug the IL code:)
Anyway, I don't really think that it's necessary, I would suggest you topost the problem you have and maybe it's possible to help you without needto decompile ExecuteReader() :)

Cheeers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"BuddyWork" <an*******@discussions.microsoft.com> wrote in messagenews:22****************************@phx.gbl...

Does anyone know if there are any articles explaining how I could debug into SqlCommand.ExecuteReader so I can see
why I am getting a particular error.

thanks

.

[BuddyWork]

Hello,

The problem is that when using SqlCommand.ExecuteReader
and the SQL statement raises an error of severity of 16
then ExecuteReader throws an exception, when you use
OdbcCommand.ExecuteReader the exception is not raised but
when you call Read() method of the OdbcDataReader you then
get the exception which is correct, basically SqlClient
does not let you call the Read method, the main problem is
that if run a Sql statement of say
'Need to create the following SP first.
create proc test
as
rollback tran
go

now run the following SQL through SqlCommand and then
OdbcCommand
begin tran
execute test
select hello="World"

you will notice that SqlCommand throws an exception on
ExecuteReader function where OdbcCommand does not, so Odbc
allows you to call Read and NextResult to go through the
recordset and retrieve your data, wher SqlClient does not
because you don't get the SqlDataReader object back.

Thanks,

-----Original Message-----
What error are you getting?

"BuddyWork" <an*******@discussions.microsoft.com> wrote in messagenews:22****************************@phx.gbl...

Does anyone know if there are any articles explaining how I could debug into SqlCommand.ExecuteReader so I can see
why I am getting a particular error.

thanks

.

[Vadym Stetsyak]

From the documentation:
"Error messages with a severity level of 10 are informational. Error
messages with severity levels from 11 through 16 are generated by the user
and can be corrected by the user"

executing test store procedure will give you error of severity 16,
"Server: Msg 3903, Level 16, State 1, Procedure test, Line 3
The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION."

so you cannot issue 'rollback' statement without preceding 'begin tran'.

"BuddyWork" <an*******@discussions.microsoft.com> wrote in message
news:27****************************@phx.gbl...

Hello,

The problem is that when using SqlCommand.ExecuteReader
and the SQL statement raises an error of severity of 16
then ExecuteReader throws an exception, when you use
OdbcCommand.ExecuteReader the exception is not raised but
when you call Read() method of the OdbcDataReader you then
get the exception which is correct, basically SqlClient
does not let you call the Read method, the main problem is
that if run a Sql statement of say
'Need to create the following SP first.
create proc test
as
rollback tran
go

now run the following SQL through SqlCommand and then
OdbcCommand
begin tran
execute test
select hello="World"

you will notice that SqlCommand throws an exception on
ExecuteReader function where OdbcCommand does not, so Odbc
allows you to call Read and NextResult to go through the
recordset and retrieve your data, wher SqlClient does not
because you don't get the SqlDataReader object back.

Thanks,

-----Original Message-----
What error are you getting?

"BuddyWork" <an*******@discussions.microsoft.com> wrote

in message

news:22****************************@phx.gbl...

Does anyone know if there are any articles explaining how I could debug into SqlCommand.ExecuteReader so I can see
why I am getting a particular error.

thanks

.

[BuddyWork]

Thanks for the reply,

But I don't think you understood my question, basically
the problem is that Odbc.ExecuteReader does NOT THROW AN
EXCEPTION whereas SqlClient.ExecuteReader does THROW AN
EXCEPTION, so because SqlClient.ExecuteReader THROWS AN
EXCEPTION there is NO WAY of retrieving the SqlDataReader
object which then means you CANNOT go through the
recordset for each MULTIPLE results returned, I've looked
at the IL code of SqlClient and can see that data is there
but SqlClient refuses you to get to it, when Odbc.Net
allows you to access the data. Please note that Odbc.Net
THROWS THE EXCEPTION when calling the READ or NEXTRESULT
method of the OdbcDataReader object.

THIS IS A BUG IN THERE CODE.

Thanks

-----Original Message-----
From the documentation:
"Error messages with a severity level of 10 are informational. Errormessages with severity levels from 11 through 16 are generated by the userand can be corrected by the user"

executing test store procedure will give you error of severity 16,"Server: Msg 3903, Level 16, State 1, Procedure test, Line 3The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION."
so you cannot issue 'rollback' statement without preceding 'begin tran'.
"BuddyWork" <an*******@discussions.microsoft.com> wrote in messagenews:27****************************@phx.gbl...

Hello,

The problem is that when using SqlCommand.ExecuteReader
and the SQL statement raises an error of severity of 16
then ExecuteReader throws an exception, when you use
OdbcCommand.ExecuteReader the exception is not raised but when you call Read() method of the OdbcDataReader you then get the exception which is correct, basically SqlClient
does not let you call the Read method, the main problem is that if run a Sql statement of say
'Need to create the following SP first.
create proc test
as
rollback tran
go

now run the following SQL through SqlCommand and then
OdbcCommand
begin tran
execute test
select hello="World"

you will notice that SqlCommand throws an exception on
ExecuteReader function where OdbcCommand does not, so Odbc allows you to call Read and NextResult to go through the
recordset and retrieve your data, wher SqlClient does not because you don't get the SqlDataReader object back.

Thanks,

>-----Original Message-----
>What error are you getting?
>
>"BuddyWork" <an*******@discussions.microsoft.com> wrote

in message

>news:22****************************@phx.gbl...
>> Does anyone know if there are any articles explaining

how

>> I could debug into SqlCommand.ExecuteReader so I can see >> why I am getting a particular error.
>>
>> thanks
>
>
>.
>

.