Just a comment : If I script my SSAS OLAP DB to xmla in SQL Server Management
Studio it comes in at some 90,000 lines. If I then go to change some part of
the xmla sqlwb.exe immediately starts hogging almost 100% cpu for several
minutes (my client pc is pentium 2.6Ghz) preventing me from working with the
file, and when I try to make mods to the file I get the same problem. The
machine is not low on memory (over 100meg available) and sqlwb.exe is not
doing any IO, just chewing up CPU. If I copy the same lines into textpad, I
have no such problem and textpad responds quickly, even with syntax
highlighting switched on.

Of course I can copy the text to textpad and work there, or I can script
different chunks of the db into different files, but both options seem
kludgey. Does anyone know why Management Studio performs so badly ? Any other
workaround to allow working with the whole file ?