Geek Answers Handbook

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

The time required to fully serialize DBMDL (to complete “Your project will be available after 10,000 operations are completed) becomes an obstacle to performance.

I did everything I could to optimize disk activity (excluding my personal TEMP folder from the antivirus scanner along with my local repository). Apart from the SSD, I'm not sure what else I can do on these lines.

I think this has something to do with how the project is organized. The finished DBMDL file is approximately 150 MB. Others in our organization do not seem to have this problem.

Did anyone have to handle this?

+4
source share
4 answers

I highly recommend upgrading to VS2010. Firstly, the construction of the model occurs in the background and does not interfere. Secondly, it ends in part time. There are many other reasons to upgrade, but performance is a killer feature for me.

+1
source

I have been looking at it again and again. If you do not compile and save the solution before closing it, then the next time you open it, it will block you. I used to have about 90 thousand operations. It got to the point that I started making coffee to leave.

In addition, I stopped closing VS2008.

+1
source

Take a look at this forum post.

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

They show that performance is much better in vs2010

+1
source

In any case, you can justify the update, this is good, but for now you can take a look at the master.dbschema file. Trimming all the fluff contained in this file worked a little with my builds with relatively little effort (30 minutes?). The article below contains the information you need.

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

0
source

More articles:


All Articles