-
Steve,
First, apologies for the performance hit. However, we've run significantly larger ORM models than this with no performace slowdowns. There is also signficant incremental work currently in progress that should alleviate any regeneration performance issues as the model gets larger.
Here are the things that take ...
-
A new release of NORMA (the December 2008 release) is now available for download.
If you have downloaded since January 5, I have added one additional fix to this package and reposted it as the 'a' release to handle a reported crashing load issue that occurred when a file contained existing duplicate constraint names. My ...
-
We have done some preliminary work to generate .EDM files from an .ORM file, but this work has not yet been blessed as sufficiently complete to add to setup.
As Ken points out, in terms of a conceptual modeling paradigm, the MS Entity Framework is basically an Entity-Relationship model. Although they like to carry the 'conceptual ...
-
The 2008 path is most likely a red herring, both the VS and NORMA products install independently.
I'd need to see a log file to provide any more conjectures. To get a setup log file:
Open a command prompt (launch cmd.exe as an administrator if you're using Vista)
Change to the directory with the expanded setup ...
-
Fixed in changeset 1330. All commands are now refreshed when a transaction completes. Included with 2008-10 CTP drop.
-
Fixed in changeset 1332. The notes editor remained enabled even when the selection did not support notes. Included with 2008-10 CTP drop.
-
Sorry, I missed the VS2005 line. You will also get this message if you try to install the wrong package, but that does not appear to be the case here.
.MSI files can be difficult to read, especially since the tool used to debug them (orca.exe) is part of a 250MB Installer SDK download. If you google 'ORCA MSDN' you'll see some hits ...
-
Are you sure you have the download that matches your Visual Studio version? Do you have VS2008 or VS2005? -Matt
-
These should map to 'Text:Large Length' and the 'Raw Data: Large Length' datatypes in the Properties Window.
I'm not sure where the CLOB came from in your snippet above. I have NCLOB in the same file.
-Matt
-
I can't say for sure, but my guess is that you had temporarily introduced a duplicate name error into the model. Adding an error of this type puts two error overlays (the !) in the model browser, but only one of them goes away when it is cleared. This is not critical, it is just outdated information.
There are five error display mechanisms, ...