Which Aspects of the Database Model Diagram Get Migrated to the ORM Source Diagram?

[John Saunders]

Often, when saving the Database Model diagram after "trivial" changes, I am
prompted to migrate the changes back to the ORM Source diagram. I usually
say "No" when I'm sure I haven't changed anything significant, because Visio
takes over my machine at 100% CPU for five or ten minutes each time I do so.

However, I just received a surprise, and it might be because I was wrong
about what I was "sure" about. I just lost some recent stored procedures.

So my questions are:

1) Are stored procedures migrated to the ORM Source model? If they are, then
I must have lost them by not migrating to the source and then doing a build.

2) What else is getting migrated to the ORM Source model that I didn't know
about?

3) Is it possible that every time I'm prompted to migrate, that Visio is
actually telling me the truth and it _does_ need to migrate something?

 

[Anthony Bloesch [MSFT]]

Always migrate changes unless you realize you made a mistake and want to
discard the changes and not save.

Anthony

--------------------
From: "John Saunders" <[email protected]>
Subject: Which Aspects of the Database Model Diagram Get Migrated to the
ORM Source Diagram?
Date: Fri, 26 Sep 2003 08:56:36 -0400
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <#[email protected]>
Newsgroups: microsoft.public.visio.database.modeling
NNTP-Posting-Host: pool-141-149-174-28.bos.east.verizon.net 141.149.174.28
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.visio.database.modeling:3146
X-Tomcat-NG: microsoft.public.visio.database.modeling

Often, when saving the Database Model diagram after "trivial" changes, I am
prompted to migrate the changes back to the ORM Source diagram. I usually
say "No" when I'm sure I haven't changed anything significant, because Visio
takes over my machine at 100% CPU for five or ten minutes each time I do so.

However, I just received a surprise, and it might be because I was wrong
about what I was "sure" about. I just lost some recent stored procedures.

So my questions are:

1) Are stored procedures migrated to the ORM Source model? If they are, then
I must have lost them by not migrating to the source and then doing a build.

2) What else is getting migrated to the ORM Source model that I didn't know
about?

3) Is it possible that every time I'm prompted to migrate, that Visio is
actually telling me the truth and it _does_ need to migrate something?
--
John Saunders
Internet Engineer
(e-mail address removed)





--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[John Saunders]

Ok, but sometimes it seems to request migration even when I haven't made any
significant changes. I was hoping for a list of which changes can cause a
request for migration. For instance, is the name of an index something which
needs to be migrated? What about rearrangements of the shapes in the
database project?