outgoing network packets going crazy!

I have two nics on my sql box. The first being a gig nic for internal networking which works fine.
The second nic however is not doing so well. It works great for a couple of hours then all of a sudden it starts sending packets out at a alarming rate. This behavior will eventually hose our entire internet in the building. The only solution at this poin
t is to reboot the sql box and everything is released at that time.
Do you have the latest service pack on there? Sounds like may be slammer:
http://www.aspfaq.com/show.asp?id=2440 SQL Slammer info
http://support.microsoft.com/default...b;en-us;816502 SP3a
additions
Andrew J. Kelly SQL MVP
"Roland Greene" <rgreene@.ipcmailwell.com> wrote in message
news:C0A25984-56A9-4937-A0F2-0F6D251BA79E@.microsoft.com...
> I have two nics on my sql box. The first being a gig nic for internal
networking which works fine.
> The second nic however is not doing so well. It works great for a couple
of hours then all of a sudden it starts sending packets out at a alarming
rate. This behavior will eventually hose our entire internet in the
building. The only solution at this point is to reboot the sql box and
everything is released at that time.
|||I have the lates SP etc. What is the best software for indentifying
slam?
Thanks in advance.
Ro
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||If you really do have the latest service packs then you don't have the
slammer as it will not work with SP3 or SP3a.
Andrew J. Kelly SQL MVP
"Roland Greene" <rgreene@.ipcmailwell.com> wrote in message
news:%23T9aD4CPEHA.3748@.TK2MSFTNGP09.phx.gbl...
> I have the lates SP etc. What is the best software for indentifying
> slam?
> Thanks in advance.
> Ro
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Roland, to verify you have SP3 or SP3a installed, what does "select
@.@.version" return?
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:uDdO3cHPEHA.2716@.tk2msftngp13.phx.gbl...
> If you really do have the latest service packs then you don't have the
> slammer as it will not work with SP3 or SP3a.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Roland Greene" <rgreene@.ipcmailwell.com> wrote in message
> news:%23T9aD4CPEHA.3748@.TK2MSFTNGP09.phx.gbl...
>

outgoing network packets going crazy!

I have two nics on my sql box. The first being a gig nic for internal networ
king which works fine.
The second nic however is not doing so well. It works great for a couple of
hours then all of a sudden it starts sending packets out at a alarming rate.
This behavior will eventually hose our entire internet in the building. The
only solution at this poin
t is to reboot the sql box and everything is released at that time.Do you have the latest service pack on there? Sounds like may be slammer:
http://www.aspfaq.com/show.asp?id=2440 SQL Slammer info
http://support.microsoft.com/defaul...kb;en-us;816502 SP3a
additions
Andrew J. Kelly SQL MVP
"Roland Greene" <rgreene@.ipcmailwell.com> wrote in message
news:C0A25984-56A9-4937-A0F2-0F6D251BA79E@.microsoft.com...
> I have two nics on my sql box. The first being a gig nic for internal
networking which works fine.
> The second nic however is not doing so well. It works great for a couple
of hours then all of a sudden it starts sending packets out at a alarming
rate. This behavior will eventually hose our entire internet in the
building. The only solution at this point is to reboot the sql box and
everything is released at that time.|||I have the lates SP etc. What is the best software for indentifying
slam?
Thanks in advance.
Ro
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||If you really do have the latest service packs then you don't have the
slammer as it will not work with SP3 or SP3a.
Andrew J. Kelly SQL MVP
"Roland Greene" <rgreene@.ipcmailwell.com> wrote in message
news:%23T9aD4CPEHA.3748@.TK2MSFTNGP09.phx.gbl...
> I have the lates SP etc. What is the best software for indentifying
> slam?
> Thanks in advance.
> Ro
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!|||Roland, to verify you have SP3 or SP3a installed, what does "select
@.@.version" return?
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:uDdO3cHPEHA.2716@.tk2msftngp13.phx.gbl...
> If you really do have the latest service packs then you don't have the
> slammer as it will not work with SP3 or SP3a.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Roland Greene" <rgreene@.ipcmailwell.com> wrote in message
> news:%23T9aD4CPEHA.3748@.TK2MSFTNGP09.phx.gbl...
>sql

OSQL -L

Hi All,
Can anyone please tell me if we issue "OSQL -L " at command prompt, does it
lists all the SQL Servers in the network or just windows servers within the
network?
Thanks,
VMIt shows you all broadcasted SQL Server instances over the net, whereas the
instances are hided for discovery.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"VM" <VM@.discussions.microsoft.com> schrieb im Newsbeitrag
news:695DABDF-AE47-430A-9AF8-1E495BBF6C7D@.microsoft.com...
> Hi All,
> Can anyone please tell me if we issue "OSQL -L " at command prompt, does
> it
> lists all the SQL Servers in the network or just windows servers within
> the
> network?
> Thanks,
> VM|||> Can anyone please tell me if we issue "OSQL -L " at command prompt, does it
> lists all the SQL Servers in the network or just windows servers within the
> network?
SQL Servers. But be carefull, because if you create an alias using Client
Network Utility, this command will list it even if the alias is not
associated with a physical server.
AMB
"VM" wrote:
> Hi All,
> Can anyone please tell me if we issue "OSQL -L " at command prompt, does it
> lists all the SQL Servers in the network or just windows servers within the
> network?
> Thanks,
> VM

OSQL -L

Hi All,
Can anyone please tell me if we issue "OSQL -L " at command prompt, does it
lists all the SQL Servers in the network or just windows servers within the
network?
Thanks,
VM
It shows you all broadcasted SQL Server instances over the net, whereas the
instances are hided for discovery.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"VM" <VM@.discussions.microsoft.com> schrieb im Newsbeitrag
news:695DABDF-AE47-430A-9AF8-1E495BBF6C7D@.microsoft.com...
> Hi All,
> Can anyone please tell me if we issue "OSQL -L " at command prompt, does
> it
> lists all the SQL Servers in the network or just windows servers within
> the
> network?
> Thanks,
> VM
|||> Can anyone please tell me if we issue "OSQL -L " at command prompt, does it
> lists all the SQL Servers in the network or just windows servers within the
> network?
SQL Servers. But be carefull, because if you create an alias using Client
Network Utility, this command will list it even if the alias is not
associated with a physical server.
AMB
"VM" wrote:

> Hi All,
> Can anyone please tell me if we issue "OSQL -L " at command prompt, does it
> lists all the SQL Servers in the network or just windows servers within the
> network?
> Thanks,
> VM

osql -L

Can anyone suggest why two client PCs on the same network report different
lists of servers using osql -L ?
Nick.
BOL says the -L option 'Lists the locally configured servers and the names
of the servers broadcasting on the network.'
So... it could be that they really are on different subnets and yuo don't
realize it. But 'locally configured' servers is the more likely answer.
-L will show all server aliases hat are defined on the client using the
Client Network Utility. You probably have different lists there...
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Nick Stephens" <NickStephens@.discussions.microsoft.com> wrote in message
news:7C1AC5D3-F374-4BFA-B220-90D97DD253F4@.microsoft.com...
> Can anyone suggest why two client PCs on the same network report different
> lists of servers using osql -L ?
> Nick.
|||My colleague and I had also discussed the possibility of different subnets
being an issue, but didn't have the tehcnical knowledge to sound out our
ideas so we moved on and in fact checked out the configs via the Client
Network Utility.
The only difference that we found was a single alias on his machine whereas
on mine the list is empty and yet there are 49 servers to be found. Maybe
there's a different list of which I'm unaware ?
Inspired by a reply to a similar post I knocked up a quick VB6 app to use
DMO and list the servers. Unsurprisingly, I got exactly the same list as with
osql -L.
However, several entries in my list differ from that when we use my
colleague's machine.
Still, at your suggestion I'll take a closer look at the configs, Biran -
many thanks for your help.
Regards, Nick.
"Brian Moran" wrote:

>
> BOL says the -L option 'Lists the locally configured servers and the names
> of the servers broadcasting on the network.'
> So... it could be that they really are on different subnets and yuo don't
> realize it. But 'locally configured' servers is the more likely answer.
> -L will show all server aliases hat are defined on the client using the
> Client Network Utility. You probably have different lists there...
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Nick Stephens" <NickStephens@.discussions.microsoft.com> wrote in message
> news:7C1AC5D3-F374-4BFA-B220-90D97DD253F4@.microsoft.com...
>
>
|||Brian, further to my initial reply to your post, we have found that it is
indeed a subnet thang. Our machines are on different subnets.
Thanks again.
Regards, Nick.
"Brian Moran" wrote:

>
> BOL says the -L option 'Lists the locally configured servers and the names
> of the servers broadcasting on the network.'
> So... it could be that they really are on different subnets and yuo don't
> realize it. But 'locally configured' servers is the more likely answer.
> -L will show all server aliases hat are defined on the client using the
> Client Network Utility. You probably have different lists there...
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Nick Stephens" <NickStephens@.discussions.microsoft.com> wrote in message
> news:7C1AC5D3-F374-4BFA-B220-90D97DD253F4@.microsoft.com...
>
>
|||You can get different results at different times from the same PC as
well due to server responses not coming back in time. OSQL -L is based
on UDP network broadcasts. There are different factors that play into
what you get back for results. You can find the issues listed at:
http://www.sqldev.net/misc/ListSQLSvr.htm
-Sue
On Thu, 4 Nov 2004 08:13:03 -0800, "Nick Stephens"
<NickStephens@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Brian, further to my initial reply to your post, we have found that it is
>indeed a subnet thang. Our machines are on different subnets.
>Thanks again.
>Regards, Nick.
>"Brian Moran" wrote:
|||Many thanks, Sue !
Nick.
"Sue Hoegemeier" wrote:

> You can get different results at different times from the same PC as
> well due to server responses not coming back in time. OSQL -L is based
> on UDP network broadcasts. There are different factors that play into
> what you get back for results. You can find the issues listed at:
> http://www.sqldev.net/misc/ListSQLSvr.htm
> -Sue
> On Thu, 4 Nov 2004 08:13:03 -0800, "Nick Stephens"
> <NickStephens@.discussions.microsoft.com> wrote:
>
>

OSQL -L

Hi All,
Can anyone please tell me if we issue "OSQL -L " at command prompt, does it
lists all the SQL Servers in the network or just windows servers within the
network?
Thanks,
VMIt shows you all broadcasted SQL Server instances over the net, whereas the
instances are hided for discovery.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"VM" <VM@.discussions.microsoft.com> schrieb im Newsbeitrag
news:695DABDF-AE47-430A-9AF8-1E495BBF6C7D@.microsoft.com...
> Hi All,
> Can anyone please tell me if we issue "OSQL -L " at command prompt, does
> it
> lists all the SQL Servers in the network or just windows servers within
> the
> network?
> Thanks,
> VM|||> Can anyone please tell me if we issue "OSQL -L " at command prompt, does it">
> lists all the SQL Servers in the network or just windows servers within th
e
> network?
SQL Servers. But be carefull, because if you create an alias using Client
Network Utility, this command will list it even if the alias is not
associated with a physical server.
AMB
"VM" wrote:

> Hi All,
> Can anyone please tell me if we issue "OSQL -L " at command prompt, does i
t
> lists all the SQL Servers in the network or just windows servers within th
e
> network?
> Thanks,
> VM

Orphaned Sessions and locks

Hi
We are using the transaction capabilities of ADO .Net. One of our tests was
to update a row in the database and break the network connection before the
transaction could be commited. This locks the row in the database for about
5 minutes before Sql Server realises that the communication has been broken,
times the transaction out and rolls it back. The question is, does anyone
know how to configure this timeout value?
Thanks
Craig
CB
Look at WAITFOR command in the BOL.
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests
was
> to update a row in the database and break the network connection before
the
> transaction could be commited. This locks the row in the database for
about
> 5 minutes before Sql Server realises that the communication has been
broken,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>
|||Hi
How did you break the conenction? Unplug the network cable?
What is your command timeout setting (not connection)?
Regards
Mike
"CB" wrote:

> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests was
> to update a row in the database and break the network connection before the
> transaction could be commited. This locks the row in the database for about
> 5 minutes before Sql Server realises that the communication has been broken,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>
>
|||The network tells sql when the connection is broken. I beleive there is a
TCP option called Keepalive. This controls how frequently TCP checks each
connection to see if it is alive - perhaps setting the keepalive to a
smaller value...
Also, you might check about connection pooling - and see if that is having
an effect ( although it should not.)
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests
> was
> to update a row in the database and break the network connection before
> the
> transaction could be commited. This locks the row in the database for
> about
> 5 minutes before Sql Server realises that the communication has been
> broken,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>
|||Yes, don't do this. This is old Client/Server technology and you should
migrate to n-Tier.
NEVER LET THE CLIENT CONTROL TRANSACTIONS. This is the number one
concurrency killer.
Batch up everything you want to do, including the BEGIN TRANS and COMMIT or
ROLLBACK logic and ship it to the SQL Server. Better yet, use nothing but
stored procedures for all of your CRUD operations.
Think through these two scenarios and tell me which one is more efficient
and faster.
Client-controlled transactions.
1. Client submits BEGIN TRAN request.
2. Request travels across network.
3. Server responds with success or failure.
4. Response travels across network.
5. Repeat process for each CRUD operation. Submit, traffic, response,
traffic.
6. Client does other processing.
7. Client submits COMMIT or ROLLBACK TRAN request.
8. Request travels across network.
9. Server responds.
10. Response travels across netowrk.
Server-controlled transactions.
1. Client submits parameters with stored procedure execution request.
2. Request travels across network.
3. Server executes transaction and all CRUD operations...very fast.
4. Response travels across network.
Hmmm? Which would you prefer? The point is about transaction processing is
that the DBMS must hold locks while the modifications are being made. You
DO NOT WANT those locks held simply because the client is having network
connections. If something should happen before the stored procedure and all
of the parameters reach the server, noting happens and the end user will
have to resubmit the request. If something should happen to the client
after the request was transmitted, the transaction still processes as if the
client were still connected. If someting happens to the server while
processing, then the ACID properties of the DBMS provide rollforward or
rollback functionality.
Sincerely,
Anthony Thomas
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
Hi
We are using the transaction capabilities of ADO .Net. One of our tests was
to update a row in the database and break the network connection before the
transaction could be commited. This locks the row in the database for about
5 minutes before Sql Server realises that the communication has been broken,
times the transaction out and rolls it back. The question is, does anyone
know how to configure this timeout value?
Thanks
Craig

Orphaned Sessions and locks

Hi
We are using the transaction capabilities of ADO .Net. One of our tests was
to update a row in the database and break the network connection before the
transaction could be commited. This locks the row in the database for about
5 minutes before Sql Server realises that the communication has been broken,
times the transaction out and rolls it back. The question is, does anyone
know how to configure this timeout value?
Thanks
CraigCB
Look at WAITFOR command in the BOL.
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests
was
> to update a row in the database and break the network connection before
the
> transaction could be commited. This locks the row in the database for
about
> 5 minutes before Sql Server realises that the communication has been
broken,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>|||Hi
How did you break the conenction? Unplug the network cable?
What is your command timeout setting (not connection)?
Regards
Mike
"CB" wrote:
> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests was
> to update a row in the database and break the network connection before the
> transaction could be commited. This locks the row in the database for about
> 5 minutes before Sql Server realises that the communication has been broken,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>
>|||The network tells sql when the connection is broken. I beleive there is a
TCP option called Keepalive. This controls how frequently TCP checks each
connection to see if it is alive - perhaps setting the keepalive to a
smaller value...
Also, you might check about connection pooling - and see if that is having
an effect ( although it should not.)
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests
> was
> to update a row in the database and break the network connection before
> the
> transaction could be commited. This locks the row in the database for
> about
> 5 minutes before Sql Server realises that the communication has been
> broken,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>|||Yes, don't do this. This is old Client/Server technology and you should
migrate to n-Tier.
NEVER LET THE CLIENT CONTROL TRANSACTIONS. This is the number one
concurrency killer.
Batch up everything you want to do, including the BEGIN TRANS and COMMIT or
ROLLBACK logic and ship it to the SQL Server. Better yet, use nothing but
stored procedures for all of your CRUD operations.
Think through these two scenarios and tell me which one is more efficient
and faster.
Client-controlled transactions.
1. Client submits BEGIN TRAN request.
2. Request travels across network.
3. Server responds with success or failure.
4. Response travels across network.
5. Repeat process for each CRUD operation. Submit, traffic, response,
traffic.
6. Client does other processing.
7. Client submits COMMIT or ROLLBACK TRAN request.
8. Request travels across network.
9. Server responds.
10. Response travels across netowrk.
Server-controlled transactions.
1. Client submits parameters with stored procedure execution request.
2. Request travels across network.
3. Server executes transaction and all CRUD operations...very fast.
4. Response travels across network.
Hmmm? Which would you prefer? The point is about transaction processing is
that the DBMS must hold locks while the modifications are being made. You
DO NOT WANT those locks held simply because the client is having network
connections. If something should happen before the stored procedure and all
of the parameters reach the server, noting happens and the end user will
have to resubmit the request. If something should happen to the client
after the request was transmitted, the transaction still processes as if the
client were still connected. If someting happens to the server while
processing, then the ACID properties of the DBMS provide rollforward or
rollback functionality.
Sincerely,
Anthony Thomas
--
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
Hi
We are using the transaction capabilities of ADO .Net. One of our tests was
to update a row in the database and break the network connection before the
transaction could be commited. This locks the row in the database for about
5 minutes before Sql Server realises that the communication has been broken,
times the transaction out and rolls it back. The question is, does anyone
know how to configure this timeout value?
Thanks
Craig

Orphaned Sessions and locks

Hi
We are using the transaction capabilities of ADO .Net. One of our tests was
to update a row in the database and break the network connection before the
transaction could be commited. This locks the row in the database for about
5 minutes before Sql Server realises that the communication has been broken,
times the transaction out and rolls it back. The question is, does anyone
know how to configure this timeout value?
Thanks
CraigCB
Look at WAITFOR command in the BOL.
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests
was
> to update a row in the database and break the network connection before
the
> transaction could be commited. This locks the row in the database for
about
> 5 minutes before Sql Server realises that the communication has been
broken,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>|||Hi
How did you break the conenction? Unplug the network cable?
What is your command timeout setting (not connection)?
Regards
Mike
"CB" wrote:

> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests wa
s
> to update a row in the database and break the network connection before th
e
> transaction could be commited. This locks the row in the database for abo
ut
> 5 minutes before Sql Server realises that the communication has been broke
n,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>
>|||The network tells sql when the connection is broken. I beleive there is a
TCP option called Keepalive. This controls how frequently TCP checks each
connection to see if it is alive - perhaps setting the keepalive to a
smaller value...
Also, you might check about connection pooling - and see if that is having
an effect ( although it should not.)
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Hi
> We are using the transaction capabilities of ADO .Net. One of our tests
> was
> to update a row in the database and break the network connection before
> the
> transaction could be commited. This locks the row in the database for
> about
> 5 minutes before Sql Server realises that the communication has been
> broken,
> times the transaction out and rolls it back. The question is, does anyone
> know how to configure this timeout value?
> Thanks
> Craig
>|||Yes, don't do this. This is old Client/Server technology and you should
migrate to n-Tier.
NEVER LET THE CLIENT CONTROL TRANSACTIONS. This is the number one
concurrency killer.
Batch up everything you want to do, including the BEGIN TRANS and COMMIT or
ROLLBACK logic and ship it to the SQL Server. Better yet, use nothing but
stored procedures for all of your CRUD operations.
Think through these two scenarios and tell me which one is more efficient
and faster.
Client-controlled transactions.
1. Client submits BEGIN TRAN request.
2. Request travels across network.
3. Server responds with success or failure.
4. Response travels across network.
5. Repeat process for each CRUD operation. Submit, traffic, response,
traffic.
6. Client does other processing.
7. Client submits COMMIT or ROLLBACK TRAN request.
8. Request travels across network.
9. Server responds.
10. Response travels across netowrk.
Server-controlled transactions.
1. Client submits parameters with stored procedure execution request.
2. Request travels across network.
3. Server executes transaction and all CRUD operations...very fast.
4. Response travels across network.
Hmmm? Which would you prefer? The point is about transaction processing is
that the DBMS must hold locks while the modifications are being made. You
DO NOT WANT those locks held simply because the client is having network
connections. If something should happen before the stored procedure and all
of the parameters reach the server, noting happens and the end user will
have to resubmit the request. If something should happen to the client
after the request was transmitted, the transaction still processes as if the
client were still connected. If someting happens to the server while
processing, then the ACID properties of the DBMS provide rollforward or
rollback functionality.
Sincerely,
Anthony Thomas
"CB" <craig.bryden@.derivco.com> wrote in message
news:enFjkvPOFHA.2748@.TK2MSFTNGP09.phx.gbl...
Hi
We are using the transaction capabilities of ADO .Net. One of our tests was
to update a row in the database and break the network connection before the
transaction could be commited. This locks the row in the database for about
5 minutes before Sql Server realises that the communication has been broken,
times the transaction out and rolls it back. The question is, does anyone
know how to configure this timeout value?
Thanks
Craig