Visual Studio Database Professional GDR R2 takes a long time to serialize DBMDL file

Question

The amount of time it takes to completely serialize the DBMDL (to finish "Your project will be available after 10000 operations are completed) is becoming a hindrance to productivity.

I've done what I can to optimize disk activity (excluding my personal TEMP folder from the virus scanner, along with my local source repository). Short of getting a SSD I'm not sure what else I can do along those lines.

I believe it has something to do with how the project is organized. The finished DBMDL file is roughly 150MB. Others throughout our organization do not seem to have this issue.

Anyone had to deal with this?

Answer 1

I have dealt with this over and over again. Unless you compile and save your solution just before you close it, the next time you open it up, it will lock you up. I used to have about 90K operations pending. It got to a point that I started making coffee runs just to get away.

Also, I stopped closing down VS2008.

Answer 2

Take a look at this forum post.

http://social.msdn.microsoft.com/Forums/en-US/vstsdb/thread/5f5fa150-c015-43a3-ab59-77737fdfb820

They indicate that performance is much better in vs2010

Answer 3

I strongly recommend upgrading to VS2010. First off, the building of the model happens in the background and doesn't interfere. Second, it finishes in a fraction of the time. There are many other reasons to upgrade as well, but performance is the killer feature for me.

Answer 4

Any way you can justify an upgrade is a good one but in the meantime you might take a look at your master.dbschema file. Trimming out all the fluff contained in this file shaved quite a bit of time off of my builds with relatively little effort (30 minutes?). The article below has the info you need.

http://blogs.msdn.com/b/bahill/archive/2009/03/23/right-sizing-the-master-dbschema-file-for-better-design-time-performance.aspx