|
|
Posted by Erland Sommarskog on 10/09/91 11:52
Zvonko (zvonko_NOSPAM_@velkat.net) writes:
> So generally, I am considering that it is far quicker to let everything
> regarding computing and large insert be done directly in the database.
> But I can not inform my user what is going on. Then I should do
> everything on a client computer. But then there is a lot of bottlenecks
> during server-client communication and a very poor performance, but my
> users get a beautifull status bar and counter and stuff. What to do, and
> what you guys are doing? Just a discussion (as this is a discussion
> board)
What we do? Write so fast code, that there is no need for progress bars! :-)
The root problem is that SQL Server does not give any progress information.
And that might be just as well. Recall that the optimizer builds the query
plan from statistics sampled about the data. From this it makes an estimate
of what is the best plan. Any progress information would be based on this
estimate. And if the estimate is wrong - which is not unusual - the progress
information would be too. I can't speak for anyone else, but personally
I find incorrect progress information to be worse than no progress
information at all.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|