Thursday, May 3, 2018 - 14:15
COZYROC has the pleasure to announce the official release of the COZYROC SSIS+ 1.8 library. In addition to the availability of many new connectors, we have invested extra effort in the overall polish of the toolkit. A new build and release process was also implemented and you will soon see improvements in both the availability and frequency of development releases and higher quality official releases. We have two announcements to make:
- Version 1.8 will be the last version with support for SQL Server 2005 and 2008. We hope this will provide enough time to our customers to make the transition to newer and greater SQL Server versions.
- Starting on June 1st, 2018 the cost of one SSIS+ Ultimate subscription becomes $479/year for new subscriptions. The price for existing subscribers stays the same, as long as their subscriptions are kept current.
Thank you for investing your hard-earned dollars in our products! Your investment is in safe hands and we will not disappoint you!
The COZYROC Team
Summary of the products available immediately for purchase:
- SSIS+ Ultimate Subscription at $399.95/Year. Starting on June 1st, 2018 the price becomes $479/year.
- SSIS+ 1.8 perpetual license at $3,999
- SAS® Adapters license at $2,499.95
- USPS Address Database / One time purchase at $299.95
- USPS Address Database / Monthly Subscription at $2,399.95/Year
- SSIS+ Premium Support at $499.95/Year
For more information, check the purchase page.
Summary of the new / updated components
- New: Support for SQL Server 2017.
- New: Support for SSDT for Visual Studio 2017.
- New: Support for Azure ADFv2 deployment.
- New: Flat File Source component will now use configured THUNK_COLUMN column length as default for all dynamic columns.
- New: Improved handling of dynamic columns in the JavaScript component.
- New: Support for Oracle Source component in SQL Server 2019.
- Fixed: Connection exhaustion because of resource leak in the system code, causing unexplained process slowdown (Thank you, Jake).
- Fixed: Failed with error "Not Found" when trying to overwrite an existing file.
- Fixed: 'Create remote directory' action in File Transfer Task will now avoid the creation of folders with same name.
- Fixed: Incorrect variable replacement in JSON.
- Fixed: Disabled various destructive commands in the script editor.
- Fixed: Improved memory consumption and management.
- Fixed: Removed not needed exception popup dialog because the error is already reported in the log.
- Fixed: Failed to retrieve "Saved Reports" resource from US-hosted service (Thank you, Hardik).
- Fixed: Failed with error "The request signature we calculated does not match the signature you provided. Check your key and signing method." (Thank you, Will).
- Fixed: If record processing failed, the composite data became misaligned from the current main record (Thank you, Andrei).
- Fixed: Failed with error "Object reference not set to an instance of an object" when processing 'ItemFulfillment' record (Thank you, Amol).
- Fixed: The bulk initialization statement was needlessly retrieving rows, slowing the process (Thank you, Irawan).
- Fixed: Failed to retrieve data from 'Billable Usage' resource (Thank you, Anna).
- Fixed: Disabled the default .NET forward-slash (/) and dot (.) unescape because it breaks connectivity to resources with such characters in use.
- Fixed: Custom -> 'Init from JSON' action didn't create a proper composite element definition.
- Fixed: MALFORMED_QUERY error in design mode when using aggregate query with LIMIT clause.
- Fixed: Failed with error "INVALID_TYPE: sObject type '...__r' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names." when trying to use relationship fields in SOQL statement (Thank you, Imran).
- Fixed: Failed with error "Object reference not set to an instance of an object" when trying to open dialog in Visual Studio 2019.
- Fixed: Failed to delete file with ampersand (&) special symbol in the name when using File Transfer Task (Thank you, Nandu).
