I’m running Sql Server Management Studio 2008 on a decent machine. Even if it is the only thing open with no other connections to the database, anything that has to do with the Database Diagram or simple schema changes in a designer take up to 10 minutes to complete and SQL Management Studio is unresponsive during that time. The same SQL code takes less than a second. This entirely defeats the purpose of the designers and diagramers.
------------------ System Information ------------------ Operating System: Windows Vista™ Ultimate (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.080917-1612) Processor: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (4 CPUs), ~2.7GHz Memory: 6142MB RAM
Please tell me this isn’t a WOW64 problem; if it is, I love MS, but step up your 64-bit support in development tools.
Is there anything I can do to get the performance anywhere near acceptable?
Edit: I’ve got version 10.0.1600.22 of SQL Server Management Studio installed. Is this not the latest release? I’m sure I installed it from an MSDN CD and I pretty much rely on Windows Update these days. Is there any place I can quickly see what the latest release version number is for tools like this?
Edit: Every time I go to open a database diagram I get the message ‘This database does not have one or more of the support objects required to use database diagramming. Do you wish to create them?’ I say yes every time. Is this part of the problem? Also, if I press the copy icon, I get the message ‘Current thread must be set to single thread apartment (STA) mode before OLE calls can be made.’ Database corruption?
It seems as though it was a network configuration problem. Never trust a developer (myself) to setup a haphazard domain at his office.
I had my DNS server on my computer pointed to my ISP’s (default because the wireless router we’re using provided by the ISP doesn’t allow me to override the DNS server to my own) instead of my DNS server here, so I have to remember to configure it manually on each computer, which I forgot for this particular computer.
I only discovered it when I tried to connect for the first time to a remote SQL Server instance form this PC. It was trying to resolve to an actual sub-domain of mycompany.com instead of my DNS server’s authority of COMPUTERNAME.corp.mycompany.com
I can’t say why this was an issue for the designers in SQL Server but not anything else, but my only hypothesis is that when I established a connection to my own computer locally using the computer name instead of ‘.’ or ‘localhost’, SQL queries executed immediately, knowing it was local, but the designers still waited for a timeout from the external IP address before trying the local one.
Whatever the explanation is, changing my DNS server for my network card on the local machine to my DNS server’s IP made it all work very quickly.