New answers tagged ssms
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.
Perhaps something in their documents\user data profile got corrupted. If you've fixed the space issue, then I suggest running a repair on the application (or installing a newer version - you can manage SQL Server 2012 with SSMS 2014, and it's free). However it may still end up being hosed because of that user's profile - if so, as a next step, you could back ...
I figured out the problem. I found that I was unknowingly running Express. I had incorrectly assumed the Express designation would be more visible withing the initial result of the @@version query In SSMS run the SELECT @@version query Grab the column edge and drag it all the way to the right. Within the copyright information it will list Express. From ...
As said in the link from comment, It's a bug in SQL Server Management Studio SQL Server 2012 Management Studio spuriously forgets password. and SQL Server Management studio solution explorer doesn't remember SQL authentication password Some alternate solutions may work for you.
I think that password is only kept during the session with BIDS.
Top 50 recent answers are included