Teradata has been working to enhance the way Incidents are created within TaYS. For the past week, we have been testing this new process internally. Starting this coming Monday, June 12th, 2017, we would like to partner with you, our valued users, to test this new process.
We are planning on releasing this to Production on June 28th, 2017. Any assistance in testing this new process would be apprecaited. If you are interested, please send me an email at firstname.lastname@example.org and I will activate your account in our Certification environment.
Subject: Support policy update for New Teradata Database Release Cadence
Teradata is continuing our technology innovation to bring the most advanced features to our customers. We are excited to announce a new database release cadence that will bring new features to our customers sooner and on a more frequent and consistent basis.
Beginning with Teradata Database software release 16.00 (planned Q1 2017), Teradata Database will follow a new release cadence, generally one release every four months.
According to the new database numbering scheme, each release will be part of a three-part series. Releases XX.00 – XX.10 – XX.20 together form a series and XX.50 – XX.60 – XX.70 together form a series.
Releases in a series have different support lifecycles as summarized below:
Series Support XX.00 – XX.10 – XX.20: • XX.00 – Code-level support for no less than four months and until the next release is General Customer Available, with fixes provided in a higher release • XX.10 – Code-level support for no less than four months and until the next release is General Customer Available, with fixes provided in a higher release • XX.20 – Code-level support for 36 months
Series Support XX.50 – XX.60 – XX.70: • XX.50 – Code-level support for no less than four months and until the next release is General Customer Available, with fixes provided in a higher release • XX.60 – Code-level support for no less than four months and until the next release is General Customer Available, with fixes provided in a higher release • XX.70 – Code-level support for 36 months
For all releases covered by an existing service contract, Teradata will continue to provide software problem resolution services even if code level support has expired.
Please refer to the Teradata Support Policy document from http://www.teradata.com/Teradata-Product-Support-Policies/, section “Teradata Database Software Support Lifecycle” for details.
TD15.00 End of Maintenance (EOM) date April 9, 2017
TD 15.00 Released on April 9, 2014 will reach End of Maintenance on April 9, 2017. End of Maintenance means that while Teradata will continue to provide the Support of Teradata 15.00, but Teradata will have discontinued Maintenance—the development and distribution of new maintenance and patch releases.
In order to achieve the highest level of availability, we recommend upgrading any system running on TD15.00, or earlier, to one of the releases currently under full Maintenance and Support. Teradata’s Database Policy is to provide a minimum three (3) years of Maintenance & Support, from the Customer General Availability date, until the End-of-Maintenance date. For TD15.00, the End-of-Maintenance date is April 9, 2017 at which time TD15.00 moves into the Support period and then the optional Extended Database Maintenance (EDM) period.
The Support period provides: preventative service, problem reporting, incident creation, down system recovery, access to knowledge articles and workarounds – no maintenance or patches are provided during the Support only period. Customers with a Maintenance & Support contract are entitled to Support past the End-of-Maintenance date and as long as the contract is renewed by Teradata and all fees are paid.
During the EDM period, Teradata offers Extended Database Maintenance service that provides the development and distribution of critical patch/efixes for a limited time. The EDM service for TD15.00 will be available for 2 years after the End-of-maintenance date -until April 9, 2019. For the first year of the TD15.00 EDM period, the EDM fee will be waived. The second year of the EDM period will be fee based. At the end of the EDM period the system would default to the Support only period. If a system remains on TD15.00 and does not contract for the EDM service prior to April 9, 2018, (Yr2 of EDM) any requests for critical patch/efixes after this date will be reviewed and, if possible, provided for a fee equal to 6 months of EDM coverage. If multiple patches are required, each patch would be subject to the same fee.
Teradata is invested in supporting your efforts to move to the latest release of the database for product enhancements and full Maintenance and Support. Please feel free to contact your Teradata representative to discuss your options.
New TaYS MyAccount/Notification Preferences
In case you missed it, users now have the ability to manage system generated alerts, incident notifications, Targeted Tech Alerts, and Knowledge subscriptions through the TaYS MyAccount/Preferences: Notifications screen. Please see KAC142F2A for additional information and description of the new notifications available now.
Existing Legacy Notification tools are planned to be discontinued September 30, 2017.