Simple Timeout Question

[James]

How can I see/set the timeout for a postback? I have a button click event
which loops through a DataSet and calls a stored procedure for every record
in the dataset. This can be a very large number, and locally it's working
fine. However, when I move to our development server, the exact same code
pointing to the same database redirects to a Page Cannot Be Displayed after
a finite period of time. I'd like to bump up the "timeout" if possible, but
I'm not sure where to do it. It's not the duration of the specific command
I'm worried about, it's the sheer number of calls.

Thanks

[sloan]

//Quote
which loops through a DataSet and calls a stored procedure for every record

in the dataset.

//End Quote

Youch.

I'm not going to give a "How to increase the Timeout" answer.
I'm going to give a "rethink that approach" answer.

If you're using Sql Server (or maybe Oracle, though I'm not a big fan of
Oracle Xml usage), you can pass in the entire
DataSet.GetXml into the stored procedure............
and process once inside the stored procedure.

If you have an index(indices) on any tables that you're updating, the Index
is being rebuilt after each and every stored procedure call.
Aka, 1000 rows in your dataset, 1000 index rebuilds.

Using the DataSet.GetXml approach, 1000 inserts = 1 index rebuild. 1000
updates = 1 index rebuild.
1000 inserts + 1000 updates = 2 index rebuilds.
You can find how to work with DataSet.GetXml
starting here:
http://www.sqlservercentral.com/colu...terproblem.asp
and
http://support.microsoft.com/?kbid=315968


"James" <mi*******@gmail.comwrote in message
news:em**************@TK2MSFTNGP04.phx.gbl...

How can I see/set the timeout for a postback? I have a button click event
which loops through a DataSet and calls a stored procedure for every

record

in the dataset. This can be a very large number, and locally it's working
fine. However, when I move to our development server, the exact same code
pointing to the same database redirects to a Page Cannot Be Displayed

after

a finite period of time. I'd like to bump up the "timeout" if possible,

but

I'm not sure where to do it. It's not the duration of the specific

command

I'm worried about, it's the sheer number of calls.

Thanks

[Halcyon]

i agree with sloan, also you can look at using atlas for queries that take a
long time, look at the cutting edge article on the msdn magazine:

http://msdn.microsoft.com/msdnmag/is...e/default.aspx

--
The walls between art and engineering exist only in our minds
"sloan" wrote:

//Quote
which loops through a DataSet and calls a stored procedure for every record

in the dataset.

//End Quote

Youch.

I'm not going to give a "How to increase the Timeout" answer.
I'm going to give a "rethink that approach" answer.

If you're using Sql Server (or maybe Oracle, though I'm not a big fan of
Oracle Xml usage), you can pass in the entire
DataSet.GetXml into the stored procedure............
and process once inside the stored procedure.

If you have an index(indices) on any tables that you're updating, the Index
is being rebuilt after each and every stored procedure call.
Aka, 1000 rows in your dataset, 1000 index rebuilds.

Using the DataSet.GetXml approach, 1000 inserts = 1 index rebuild. 1000
updates = 1 index rebuild.
1000 inserts + 1000 updates = 2 index rebuilds.
You can find how to work with DataSet.GetXml
starting here:
http://www.sqlservercentral.com/colu...terproblem.asp
and
http://support.microsoft.com/?kbid=315968


"James" <mi*******@gmail.comwrote in message
news:em**************@TK2MSFTNGP04.phx.gbl...

How can I see/set the timeout for a postback? I have a button click event
which loops through a DataSet and calls a stored procedure for every

record

in the dataset. This can be a very large number, and locally it's working
fine. However, when I move to our development server, the exact same code
pointing to the same database redirects to a Page Cannot Be Displayed

after

a finite period of time. I'd like to bump up the "timeout" if possible,

but

I'm not sure where to do it. It's not the duration of the specific

command

I'm worried about, it's the sheer number of calls.

Thanks

[James]

Understood, obviously...but I have no control over said stored
procedure/database. I'm also unable to bargain with those responsible for
aforementioned structure. I'm stuck dealing with what I have,
unfortunately.

"Halcyon" <Ha*****@discussions.microsoft.comwrote in message
news:AF**********************************@microsof t.com...

>i agree with sloan, also you can look at using atlas for queries that take
a
long time, look at the cutting edge article on the msdn magazine:

http://msdn.microsoft.com/msdnmag/is...e/default.aspx

--
The walls between art and engineering exist only in our minds
"sloan" wrote:

>//Quote
which loops through a DataSet and calls a stored procedure for every
record

in the dataset.

//End Quote

Youch.

I'm not going to give a "How to increase the Timeout" answer.
I'm going to give a "rethink that approach" answer.

If you're using Sql Server (or maybe Oracle, though I'm not a big fan of
Oracle Xml usage), you can pass in the entire
DataSet.GetXml into the stored procedure............
and process once inside the stored procedure.

If you have an index(indices) on any tables that you're updating, the
Index
is being rebuilt after each and every stored procedure call.
Aka, 1000 rows in your dataset, 1000 index rebuilds.

Using the DataSet.GetXml approach, 1000 inserts = 1 index rebuild. 1000
updates = 1 index rebuild.
1000 inserts + 1000 updates = 2 index rebuilds.
You can find how to work with DataSet.GetXml
starting here:
http://www.sqlservercentral.com/colu...terproblem.asp
and
http://support.microsoft.com/?kbid=315968


"James" <mi*******@gmail.comwrote in message
news:em**************@TK2MSFTNGP04.phx.gbl...

How can I see/set the timeout for a postback? I have a button click
event
which loops through a DataSet and calls a stored procedure for every

record

in the dataset. This can be a very large number, and locally it's
working
fine. However, when I move to our development server, the exact same
code
pointing to the same database redirects to a Page Cannot Be Displayed

after

a finite period of time. I'd like to bump up the "timeout" if
possible,

but

I'm not sure where to do it. It's not the duration of the specific

command

I'm worried about, it's the sheer number of calls.

Thanks

[Halcyon]

mkay, are you able to use atlas?

i use it for a web based software metering application that can take hours
to complete and it can take hours to complete, the atlas approach worked for
me, lemme know if it grafts for you ; )

--
The walls between art and engineering exist only in our minds
"James" wrote:

Understood, obviously...but I have no control over said stored
procedure/database. I'm also unable to bargain with those responsible for
aforementioned structure. I'm stuck dealing with what I have,
unfortunately.

"Halcyon" <Ha*****@discussions.microsoft.comwrote in message
news:AF**********************************@microsof t.com...

i agree with sloan, also you can look at using atlas for queries that take
a
long time, look at the cutting edge article on the msdn magazine:

http://msdn.microsoft.com/msdnmag/is...e/default.aspx

--
The walls between art and engineering exist only in our minds
"sloan" wrote:

//Quote
which loops through a DataSet and calls a stored procedure for every
record
in the dataset.
//End Quote

Youch.

I'm not going to give a "How to increase the Timeout" answer.
I'm going to give a "rethink that approach" answer.

If you're using Sql Server (or maybe Oracle, though I'm not a big fan of
Oracle Xml usage), you can pass in the entire
DataSet.GetXml into the stored procedure............
and process once inside the stored procedure.

If you have an index(indices) on any tables that you're updating, the
Index
is being rebuilt after each and every stored procedure call.
Aka, 1000 rows in your dataset, 1000 index rebuilds.

Using the DataSet.GetXml approach, 1000 inserts = 1 index rebuild. 1000
updates = 1 index rebuild.
1000 inserts + 1000 updates = 2 index rebuilds.
You can find how to work with DataSet.GetXml
starting here:
http://www.sqlservercentral.com/colu...terproblem.asp
and
http://support.microsoft.com/?kbid=315968


"James" <mi*******@gmail.comwrote in message
news:em**************@TK2MSFTNGP04.phx.gbl...
How can I see/set the timeout for a postback? I have a button click
event
which loops through a DataSet and calls a stored procedure for every
record
in the dataset. This can be a very large number, and locally it's
working
fine. However, when I move to our development server, the exact same
code
pointing to the same database redirects to a Page Cannot Be Displayed
after
a finite period of time. I'd like to bump up the "timeout" if
possible,
but
I'm not sure where to do it. It's not the duration of the specific
command
I'm worried about, it's the sheer number of calls.

Thanks