100% CPU After Migrating Changes to Source Models

[John Saunders]

I have a simple setup. I've got a database project with a single ORM Source
Model. It all seemed happy, as I had earlier in the day done a Generate
successfully and with no warnings.

I then added a function and stored procedure via the New button in the Code
window. I Updated them into the database and tested them. I had to make a
few changes in the database, and since Update isn't working well in the
opposite direction, I made those changes to the model by hand.

I then typed Control-S in the database model to save the changes. Of course,
it asked me if I wanted to migrate the changes to the Source Models.
Although I suspected there were no changes, I said Yes. This proceeded
normally (though there was a warning about the function).

After the "Migrate complete, 0 errors 1 warning" message, Visio began taking
up 100% CPU on my 1.5Ghz system. This went on for over five minutes.

This is not an isolated incident. In fact, it happens most of the time.

Is there something I can do about this? It's more than annoying. It makes me
not want to save my changes.

 

[John Saunders]

No clues?

 

[Scot A. Becker]

Hi John,

Sorry... I have been meaning to respond about this, but was busy....

I have seen things like this before too; I have found the migrate changes
functionality to be unstable. I am told it just takes along time and given a
couple of days it will finish. ; )

For this (and other) reason(s), I never make structural changes at the
logical level and instead make the equivalent changes to the ORM Source
models and re-build the model. When you have to make the inevitable naming
changes, use the Update Models menu option and always say no to the migrate
prompt.

If you aren't using the latest version, consider patching/obtaining it (if
possible) as some of the related bugs were supposedly fixed in later
versions.

See also: http://www.orthogonalsoftware.com/tips.html#4

I haven't tried it with changing SPs (which obviously have no ORM Source
component), however, so this might not help.

Hope that helps,
Scot.
................................................
Scot Becker

Orthogonal Software
www.orthogonalsoftware.com

 

[John Saunders]

Hi John,

Sorry... I have been meaning to respond about this, but was busy....

I have seen things like this before too; I have found the migrate changes
functionality to be unstable. I am told it just takes along time and given a
couple of days it will finish. ; )

For this (and other) reason(s), I never make structural changes at the
logical level and instead make the equivalent changes to the ORM Source
models and re-build the model. When you have to make the inevitable naming
changes, use the Update Models menu option and always say no to the migrate
prompt.

If you aren't using the latest version, consider patching/obtaining it (if
possible) as some of the related bugs were supposedly fixed in later
versions.

See also: http://www.orthogonalsoftware.com/tips.html#4

Thanks, Scot, Update Source Models it is!