can you profile and check if only this procedure is getting called when report is rendered? It may be that there are some other datasets also involved in it which may call some other code as well in parallel.
Hi Vishakh, Yes I did check and that's not the case. The report is hosted on a .NET page.
We also found - it runs on another backup server fine, but times out on the server where it's deployed now. That indicates - it's not any coding or procedure issue. It's something to do with other factors associated with the server.