running on the server with SQL Agent) it really doesn't pay to FORCE the
connection to use TCP sockets, with a TCP alias. Since the connection is
local to the server, the SQL Server can utilize Shared memory or Local
pipes and never touch the network.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.ok. I'll try tonight to run the job with Name Pipe
Activated. I give you a feelback tomorrow.
thanks
quote:
>--Original Message--
>When connections are being made on the local server (as
with local jobs
quote:
>running on the server with SQL Agent) it really doesn't
pay to FORCE the
quote:
>connection to use TCP sockets, with a TCP alias. Since
the connection is
quote:
>local to the server, the SQL Server can utilize Shared
memory or Local
quote:
>pipes and never touch the network.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
quote:|||Ok now after 10 days I can tell you I don't received
>
>.
>
again the General NEtwork Error.
But now I got some type of lock like LCK_M_S, OLEDB,
CXPACKET...
How I can eliminate this Wait Type ?
quote:
>--Original Message--
>When connections are being made on the local server (as
with local jobs
quote:
>running on the server with SQL Agent) it really doesn't
pay to FORCE the
quote:
>connection to use TCP sockets, with a TCP alias. Since
the connection is
quote:
>local to the server, the SQL Server can utilize Shared
memory or Local
quote:
>pipes and never touch the network.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
quote:
>
>.
>
No comments:
Post a Comment