Re: SqlCommand.Cancel and Transactions
- From: "draggin dragon" <james.tsao@xxxxxxxxx>
- Date: 28 Feb 2007 05:24:38 -0800
Thanks for the response.
1. What's PSS?
2. Can you provide some insight on what SqlCommand.Cancel does? Why
is it that my connection/transaction sometimes unusable, albeit
infrequently.
3. TOP is undesirable because of our given architecture. There are
issues when used in conjunction with orderby and other more esoteric
issues.
thanks again.
JT
On Feb 28, 5:44 am, "Miha Markic [MVP C#]" <miha at rthand com> wrote:
Seems like you have the worst case problem. I guess you have two options
here:
- Call PSS
- use TOP statement
I guess the later is easier. BTW why are you opposed to using TOP
statements - you mentioned performance and complexity but I don't relly see
any of the two or at least it shouldn't be a huge problem.
--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & developmentwww.rthand.com
Blog:http://cs.rthand.com/blogs/blog_with_righthand/
.
- References:
- SqlCommand.Cancel and Transactions
- From: draggin dragon
- SqlCommand.Cancel and Transactions
- Prev by Date: Re: query question
- Next by Date: Re: Joining tables from two databases
- Previous by thread: SqlCommand.Cancel and Transactions
- Next by thread: Re: SqlCommand.Cancel and Transactions
- Index(es):
Loading