When watching results in SQL Profiler, does the RPC Complete include time to send results to the client? Or is it just the time the server spent gathering the records?
The reason I'm asking is I'm working on a program to move a large amount of data. The databases are cloud hosted in Azure, and the code is (currently) running locally. I can see the RPC call times in SQL Profiler, and the query to select the rows isn't cheap (massive table filtered by an indexed column then sorted by the table's primary key for paging results), and it isn't an insignificant amount of data (100k records per page, some situations I'm moving up to 60 million records per run).
I'm curious if I should expect it to run faster once the code is running inside Azure. If the RPC complete timing includes the time spent for the data to be sent to the client, this should decrease some (I'm hoping dramatically). If the RPC complete timing is just the time for the server to select the data, then I won't see much of an increase when it's running inside Azure.