Fix for DbEngine when deploying SPROCS for non-dbo schemas


Author
Message
Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
After testing, another minor bug was found when deploying using the previous fix to a database that did not have the extended property set.  This attachment fixes the error.
Attachments
StrataFrameDbEngine.zip (470 views, 92.00 KB)
Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
In the 1.6.5 build, we changed the DDT to use extended properties on the database, stored procedures, views,and UDFs so that in environments where there may be a DBA they can add their own without being removed the next time the meta-data was deployed.  In doing so, we accidentally introduced a bug related to those extended properties.  So now, when a schema other than DBO was being used, the DDT did not "see" the extended properties and thus did not remove them prior to attempting to re-deploy them which resulted in an error.  This issue has been resolved with this assembly.  Extract the attached ZIP and do the following:
  1. Close the DDT and Visual Studio
  2. Copy the DLL and XML both to the c:\program files\common files\microfour\strataframe folder
  3. Drag the DLL into the GAC (c:\windows\assembly)
  4. Go back into Visual Studio and/or the DDT and redeploy your package.  The error should be resolved.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search