July 28, 2003 at 1:14 pm
We have one server very heavy using remote transaction, after service pack 3 apply, some of our applications have lots transaction error, and we open the ticket with Microsoft, and after talk with them 2 month, and still can not resolve them, once a while the error still come back(like unable to begin a distributed transaction, or sometime is connection is busy with result for another command).
We now consider add startup parameter -g 512 and do you think could resolve this issure
feifei liu
Rachel
July 31, 2003 at 8:00 am
This was removed by the editor as SPAM
August 2, 2003 at 10:01 am
I'd be surprised, but it doesn't hurt to try. Considered going back to SP2? By remote transaction you mean one from another SQL Server, or a distributed transaction, both?
Andy
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply