I am getting the same message. I am running Vista Business (32-bit), with SQL Server 2005 SP2 (9.0.3054).
Twice in the last 30 minutes, SSMS (Sql Server Management Studio) hung after I saved a Database Diagram.SSMS sits there and eventually Vista provides a message in the toolbox titled "is Busy" that says "Microsoft SQL Server Management Studio is waiting for an internal operation to complete. If you regularly encounter this delay during normal usage, please report this problem to Microsoft".
The database that I am in was created 60 minutes ago, and I was using the Database Diagrams to create new tables. I have only four so far. I would have many more by now, if only SSMS would stop hanging. The last time it hung (15 minutes ago) I just let it go. It still has the animated "saving" icon going as I type this message. So thestatement from Jonathan that it "takes time to process",is not a helpful answer. (20 minutes now of SSMS still trying to save)
So, I'm wondering who else has this problem. I never had this problem running SSMS on Windows XP, except when I forgot to install SP2. Once I installed SP2, that problem went away.
However, my current instance (like I said above) is Vista Business (32-bit), with SQL Server 2005 SP2 (9.0.3054), so it should not be having this problem.
(25 minutes into SSMS trying to save).
Any ideas out there?
The first time this happened, I killed the SqlWb.exe process, and restarted SSMS. I found that the diagram had not saved, but the tables that were new had been created. So I created the diagram again, and put the tables into it. The problem re-occured when I created a new diagram and created a new table again and tried to save (which would create two SQL Server objects objects - table and a diagram). So, my best guess is that when you create Diagrams, save them prior to creating new tables on the diagram.
(30 minutes into SSMS trying to save).
I just took a dump of the SqlWb.exe process, and killed it, again.
Any ideas?