Any plans to implement SQL logging in the data adapters? It seems like a
very basic feature. It would help with debugging if one could view the
actual SQL statements that get generated when one does something like:
DataAdapter.Update(SomeDataTable);

Or, is the feature there and I have just overlooked it?

SQL Server Profiler...

"John Viele" <johnv@{NO_SPAM}goisc.com> wrote in message
news:%(E-Mail Removed)...
> Any plans to implement SQL logging in the data adapters? It seems like a
> very basic feature. It would help with debugging if one could view the
> actual SQL statements that get generated when one does something like:
> DataAdapter.Update(SomeDataTable);
>
> Or, is the feature there and I have just overlooked it?
>
>

Sorry, but SQL Profiler is a royal P.I.T.A. Regardless, it is not what I
need. It's too difficult to get it to produce the narrow kind of trace
information I am trying to get. I simply need the ability to see the
specific statement(s) generated when a data adapter performs a SQL
statement, particularly inserts, updates, and deletes. That's when it has
to plug in values from the data table's rows.

In addition, I have tried to use it for this application, but it does not
record any of the SQL activity performed by the Windows Service I am
debugging, though it DOES record anything I do manually in the same
database.

"Kristofer Andersson" <(E-Mail Removed)>
wrote in message news:(E-Mail Removed)...
> SQL Server Profiler...
>
> "John Viele" <johnv@{NO_SPAM}goisc.com> wrote in message
> news:%(E-Mail Removed)...
> > Any plans to implement SQL logging in the data adapters? It seems like
a
> > very basic feature. It would help with debugging if one could view the
> > actual SQL statements that get generated when one does something like:
> > DataAdapter.Update(SomeDataTable);
> >
> > Or, is the feature there and I have just overlooked it?
> >
> >
>
>

Ok, the user iterface in SQL profiler could be nicer but with the right
filters set it will get you the data you need. Try with filters on
loginname, clientprocessid or textdata. A filter on textdata is very
efficient...

"John Viele" <johnv@{NO_SPAM}goisc.com> wrote in message
news:(E-Mail Removed)...
> Sorry, but SQL Profiler is a royal P.I.T.A. Regardless, it is not what I
> need. It's too difficult to get it to produce the narrow kind of trace
> information I am trying to get. I simply need the ability to see the
> specific statement(s) generated when a data adapter performs a SQL
> statement, particularly inserts, updates, and deletes. That's when it has
> to plug in values from the data table's rows.
>
> In addition, I have tried to use it for this application, but it does not
> record any of the SQL activity performed by the Windows Service I am
> debugging, though it DOES record anything I do manually in the same
> database.
>