|
|
Important Note: The DDL Archive Utility is based on Microsoft SQL Server's Distributed Management Objects (DMO), a Component Object Model (COM) technology. SQL Server 7 and SQL Server 2000 are fully feature supported by DMO. However, due in some part to the instability that COM can wreck on the operating environment, the DMO libraries were not updated to support features new with SQL Server 2005. The DMO library was updated, but only enough to get a Primary Interop wrapper so it could continue to work as it did with SQL Server 2000 when used on SQL Server 2005. So, while the DDL Archive Utility is still available, it will not be updated and will eventually die when DMO support is removed from a future SQL Server release. For most of us not a problem because the advantages to using SQLClue are overwhelming. (See for yourself!) SQLClue uses SQL Server Management Objects (SMO): DMOs managed (.NET) code replacement. Not only does SQLClue support and document the technologies introduced with SQL Server 2005 and extented in SQL Server 2008, it also uses many of those new capabilities for huge archiveal performance gains, encryption support, and a highly configurable archival process. See the comparison of SQLClue and the DDL Archive Utility for more details. Bill Wunder's DDL Archive Utility Archive DDL changes to SourceSafe
The Archive Utility FAQ
Download the latest version of Bill Wunder's DDL Archive Utility for evaluation or upgrade to the above release if you have previously downloaded the utility at www.sqlservercentral.com. I think you can still get the utility at www.sqlservercentral.com but I'm not having much luck making a newer version available from there (hopefully I didn't offend anyone). If you have an older version installed, be sure to uninstall it before you install the latest build. Uninstalling will not affect your configuration or your SourceSafe files.
2-1-2004 - Users running only SQLXML 3.0 SP1 or SP2 must configure the SqlXml assembly to allow the Archive Utility application to use the upgraded assembly version. Alternately, users running SP2 can install the latest version of the DDL Archive Utility and may also want/need to remove any previous versions from the .Net assembly cache on the Archive Utility host machine. See Using The .Net Framework 1.1 Configuration Tool - A DBAs window into the Global Assembly Cache for additional information.
3-23-2004 - two users reported an "unhandled exception" error at application startup. I could not reproduce the problem but added error handling to the code that uses the SQLDMO.Application through the .Net generated INTREROP.SQLDMO Assembly to load the list box with available SQL Server instance names. From VB Script both users were able to access and use the SQLDMO.Namelist via the Scripting Host however through the .Net INTEROP assembly it was determined that the error, "Query Interface for interface SQLDMO.NameList failed" was caught. I modified the list box population box to bail out of the attempt to load the list box and just allow the user to type in server names if this error occurs. This seems to have both people able to generate an archive. (v 4.2.2)
4-10-2004 - A problem has been reported that prevents a successful install of the utility if SourceSafe is not installed in the default location. I'm changing this so that the utility will install without SourceSafe, the SQL Client Utilities, or SQLXML installed and will instead give you run time errors that should make it clear what the problem is if any of these items are missing.
known bug list:
Bug: Previous version is not uninstalled when installing a new version.
Workaround: Uninstall the previous version before installing the latest release.
Bug: Sometimes during delete processing files in a collection are deleted from SourceSafe that still exist in the SQL Server Database. Seems to happen to all the files in the current collection in alphabetical order after multiple deletes from that collection. For example if you delete the stored procedures "dbo.proc1" and "dbo.proc2" from SQL Server database A, you may see that "dbo.proc3.PRC" and "dbo.zzproc.PRC" are also logically deleted from SourceSafe and and logged to ArchUtilChanges table as deleted even though the procedures "dbo.proc3" and "dbo.zzproc" still exist in the database being archived.
Workaround: During the next execution of the Archive Utility the incorrectly deleted files will be recovered.
Bug: The error "Object Reference not set to an instance of an Object" may be logged to the Application Event log of the Archive Utility host machine. I have only seen this from ArchCon.EXE.
Workaround: none needed. I don't believe this error has any effect on the proper operation of the utility.
Bug: The procedures created in instArchUtil.sql may include references to to my implementation of SMTP email that replaces xp_send mail.
You can add the SMTP email subsystem by following these guidelines or you can replace the reference to sysmon.dbo.safe_sendmail with a master.dbo.xp_sendmail if you prefer to stick with the MAPI email implementation included with SQL Server 7/2000. |
|
|