Profiler ....duration

In SQL Server 2000, "Duration" in profiler (which is in milliseconds) taken by the event; does it include time for the network transfer of the results to the client as well ; or its just the duration taken by SQL Server to complete the SQL Statement.All the measurements are serverside only, so no network time. If you want to see the network time then run the query in query analyser but before you start right click and select client side statistics.|||

thanks for the info.

I have a 3rd party application & the queries are generated from the application.

So I wanted to see the total duration. Queries are very dynamic, so running from Query Analyzer may not yield same result w.r.t. time/ network load when the app runs/ etc etc ... So i am trapping it in profiler.

|||Then there is no easy way to get this with the built in tools.

Production Replication and Linked Server Failure

Replication between remote offices, along with linked servers, began failing. Network and server admins indicate that nothing has been changed. The DBA of the remote server also says nothing has been changed. Replication failes with the following message.

The process could not connect to Subscriber 'ProdServer1\Production1'.

SQL Server does not exist or access denied.
(Source: CDB0202\PRODUCTIONLFG (Data source); Error number: 17)

I am able to connect to the remote server using EM and Query Analyzer. I am also able to create linked servers from the local production server to a remote test server.

Any tips on how to troubleshoot this problem?

Thanks, DaveThe problem has been resolved. WINS had expired on the clustered remote server. The network admins don't understand why it happened and can't explain why DNS didn't didn't resolve the name, but at least it is fixed. I'm a bit confused why EM and Query Analyzer did not experience any problems.

Thanks, Dave

Processor Busy

When my Windows 2000 server is idle the whole processor is used by SQL Server 2000 and all switches and hubs on the network show collisions continuously. When some load comes on server it becomes normal. Can anybody suggest solution.Howdy,

Try removing all network protocols except TCPIP and see what happens.

Also, make sure the OS knows what its local default gateway is ( open command prompt & type ipconfig /all ) , otherwise it may trying broadcasts to find other servers on the network and so give you lots of network traffic.

Cheers,

SG.

Process order for changing IPs of network adapters and SQL services

A change in networking if forcing all of our IPs to change. I have
found KB articles 230356 and 244980 with the processes for changing the
IP addresses of the network adapters and SQL virtual servers
separately, but I would like to make sure I have the overall process
order correct.
Is there documentation available that describes the steps when _all_ of
the IPs involved in a cluster change, both physical and virtual?
Ouch. I went through this once before. While I don't have a step-by-step
process, the key is to only mess up one network at a time. Make sure you
have enabled private communications on both the public and private cluster
networks. While you are changing one network the cluster can continue to
communicate on the other one. Make sure the cluster can communicate on the
modified network before changing the unmodified one.
My biggest problem was changing the IP addresses of the SAN and re-linking
to the host nodes.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<bsg075@.gmail.com> wrote in message
news:1124126624.137059.189680@.z14g2000cwz.googlegr oups.com...
>A change in networking if forcing all of our IPs to change. I have
> found KB articles 230356 and 244980 with the processes for changing the
> IP addresses of the network adapters and SQL virtual servers
> separately, but I would like to make sure I have the overall process
> order correct.
> Is there documentation available that describes the steps when _all_ of
> the IPs involved in a cluster change, both physical and virtual?
>