Does the SQLDatasource control produce a disconnectected recordset?

[John Kotuby]

Hi all,
I am relatively new to ASP.NET 2.0 programming. I have some experience with
classic ASP and VB6. In Visual Web Developer (VS 2005) there a numerous ways
to work with data. In my application I am using a number of them, including
the SQLDataAdapter, DataTables, etc.

On one page I have chosen to use the SQLDatasource in conjunction with an
ASP Repeater control, because it was by far the quickest implementation for
my needs. However, I want to make sure I am getting a disconnected recordset
to work with. One that has closed the connection to the DB Server and will
not place any kinds of locks on the DB that might impede other users who
need exclusive locks to write to the table.

I have not found an answer for this question in the 4 books I have purchased
or in the VS 2005 documentation.

Thanks all in advance...

[Mark Fitzpatrick]

You can determine whether the item will be disconnected based upon which
type of resultset it returns. If it returns a dataset should be disconnected
because it is composed of datatables. A datatable is always loaded and then
it releases the connection. A DataReader is connected until it is closed and
pretty much always connected until you're done with it. The SQLDatasource
has a property called DataSourceMode that can be used to determine which it
will use, a DataSet or a DataReader. Go for the DataSet as that should give
you load it and release it data method.
--

Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"John Kotuby" <jo***@powerlist.comwrote in message
news:uu**************@TK2MSFTNGP06.phx.gbl...

Hi all,
I am relatively new to ASP.NET 2.0 programming. I have some experience
with classic ASP and VB6. In Visual Web Developer (VS 2005) there a
numerous ways to work with data. In my application I am using a number of
them, including the SQLDataAdapter, DataTables, etc.

On one page I have chosen to use the SQLDatasource in conjunction with an
ASP Repeater control, because it was by far the quickest implementation
for my needs. However, I want to make sure I am getting a disconnected
recordset to work with. One that has closed the connection to the DB
Server and will not place any kinds of locks on the DB that might impede
other users who need exclusive locks to write to the table.

I have not found an answer for this question in the 4 books I have
purchased or in the VS 2005 documentation.

Thanks all in advance...

[John Kotuby]

Thanks muchly Mark..

That's what I needed.
.... John

"Mark Fitzpatrick" <ma******@fitzme.comwrote in message
news:Ow**************@TK2MSFTNGP05.phx.gbl...

You can determine whether the item will be disconnected based upon which
type of resultset it returns. If it returns a dataset should be
disconnected because it is composed of datatables. A datatable is always
loaded and then it releases the connection. A DataReader is connected
until it is closed and pretty much always connected until you're done with
it. The SQLDatasource has a property called DataSourceMode that can be
used to determine which it will use, a DataSet or a DataReader. Go for the
DataSet as that should give you load it and release it data method.
--

Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"John Kotuby" <jo***@powerlist.comwrote in message
news:uu**************@TK2MSFTNGP06.phx.gbl...

>Hi all,
I am relatively new to ASP.NET 2.0 programming. I have some experience
with classic ASP and VB6. In Visual Web Developer (VS 2005) there a
numerous ways to work with data. In my application I am using a number of
them, including the SQLDataAdapter, DataTables, etc.

On one page I have chosen to use the SQLDatasource in conjunction with an
ASP Repeater control, because it was by far the quickest implementation
for my needs. However, I want to make sure I am getting a disconnected
recordset to work with. One that has closed the connection to the DB
Server and will not place any kinds of locks on the DB that might impede
other users who need exclusive locks to write to the table.

I have not found an answer for this question in the 4 books I have
purchased or in the VS 2005 documentation.

Thanks all in advance...