Tag Info

New answers tagged


From at least SQL Server 2008 R2 SQL Server comes with an understanding of HTML. http://msdn.microsoft.com/en-us/library/ms142499.aspx says: " SQL Server installs its own XML and HTML filters. In addition, any filters for Microsoft proprietary formats (.doc, .xdoc, .ppt and so on) that are already installed on the operating system are also loaded by SQL ...


I was having "timeout" issue when trying to connect to SQL Server 2000 using Management Studio 2012. Finally the solution for me was to install Microsoft SQL Server 2000 Service Pack 4 - http://www.microsoft.com/en-ca/download/details.aspx?id=18290 I hope that this solution can be useful for someone having this problem.


On server side trace DURATION is the total execution time (in ms) of a query. CPU column will provide you time on CPU (total of one or multiple CPUs). While DURATION - CPU = IO Time So If RPC-Completed time for single procedure call or total time is according to benchmarks then problem could be on network side. Where is actual problem. To get this you must ...


If you expand the SQL Server Agent in SSMS and double click the Job Activity Monitor you should see what you need.


Client processing time is the amount of time spent in milliseconds between the first received response packet and the last received response packet by the client. When you run the query in SSMS it render the data row by row to the GUI. Your application doesn't do that. Setting the SSMS option to Discard results after execution will eliminate the time ...


SSMS renders the data retrieved from your query into a grid and fetches some metadata about the query (rows affected, duration, etc.). Those features and the rendering of the datagrid may cause a query to end slower in SSMS than directly from the .Net code which doesn't have a rendering part and only retrieves a Datatable/Dataset.

Top 50 recent answers are included