Thanks both of you! I should have thought of: "Forcing a connection timeout could be as simple as adding a fake ip address to the hosts file on the test client machine for the DB Server"
That was the ticket.
-MK
Glad to help, and I hope your debugging goes well!
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
mister.magoo (4/29/2014)
Grant Fritchey (4/29/2014)
Try using the WAITFOR command in T-SQL. That'll pause the execution of the query and you should see a timeout.Except that will be a Command Timeout, not a Connection Timeout.
Forcing a connection timeout could be as simple as adding a fake ip address to the hosts file on the test client machine for the DB Server, so that it never connects OR creating an alias on the client machine to achieve the same misdirection.
Well, the command shouldn't time out with defaults set within SQL Server, but your answer is what the OP wanted.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply