Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
acegik
Starting Member
3 Posts |
 Posted - 2009-03-31 : 20:10:00
|
| Hi All,I'm fairly new to SSMS and have experienced some frustratingly long delays when opening various dialogs. For example:If I right click a database->tasks->export data… it takes 1min 40sec for the dialog to appear.Opening a job then going to steps->edit - it takes 45sec for the dialog to appearIt doesn't seem to make a difference if the database is empty or loaded up with data. In contrast, on the instance of SQL server 2005 on my desktop, it takes 5 seconds for the first of the dialogs noted above to appear. Regular DML queries are not noticably slow.The problematic instance is a VM running 64bit Windows 2003 Server on ESX with 16GB RAM and 4 E5450 CPU cores available. The systems administrators are starting to push back saying that this is normal performance but just wanting to check with other users of SS2005 whether they get similar response times? Thanks,NR |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
acegik
Starting Member
3 Posts |
Posted - 2009-03-31 : 21:35:41
|
| One of the sys admins found a known issue about this - http://sql-server-performance.com/Community/forums/p/2148/2148.aspx<quote>The "solution" is to disable the CRL check in IE.Open Internet ExplorerGo to Tools -> Internet Options -> AdvancedIn the Security section uncheck "Check for publisher's certificate revocation" </quote>This has dramatically reduced the time to open SQL Server and also makes the export wizard come up almost instantly for _most_ users. I'm still trying to work through an issue where its still takes 30s for some users, but I think that might be related to some configuration of their profiles/DB privs. Will post again if I resolve that one.Thanks,NR |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
acegik
Starting Member
3 Posts |
Posted - 2009-04-01 : 19:13:52
|
| Thanks Tara, due to the nature of the organisation and the particular environment, it can be a little convoluted getting SPs applied. Since the sys admin found this solved most of the immediate issue, it didn't seem necessary to apply the SP update with the same urgency. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2009-04-01 : 19:17:41
|
| Keep in mind that I'm not saying to install the service pack to update the database engine. I'm saying to install it on the client machine. Service packs contain bug fixes for SSMS and other client tools as well as updates to the database engine (the actual instance). The sysadmin should have no opinion about a service pack installation on a client machine.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog"Let's begin with the premise that everything you've done up until this point is wrong." |
|
|
|
|
|
|
SQL Server 2005 dialogs seem slow. Is this normal?