Package Submission Program

Package Submission Program

  • Comments 1

Anjan Das (SSIS Program Manager) has posted about the SSIS Package Submission Program in the forums. The goal of the program is to further test out our 2005 to 2008 upgrade process, and identify any issues prior to RTM.

Here are all the details:

THE MICROSOFT SQL SERVER 2005
INTEGRATION SERVICES (SSIS) PACKAGE SUBMISSION PROGRAM

The following are terms and conditions regarding your participation in the Microsoft SQL Server 2005 Integration Services (SSIS) Package Submission program (the “Program”) and is a contract between you, the entity that participates in this program (“you” or “your”), and Microsoft Corporation, a Washington corporation (“Microsoft”).  Sometimes Microsoft is referred to as “we,” “us” or “our”. By submitting an SSIS package (described in more detail below), you agree to the following terms and conditions:

1.      PROGRAM DESCRIPTION

The object of this Program is to provide the Microsoft SQL Server development team with a variety of interesting SSIS packages generated from SQL Server 2005 on which to test our new release(s) of SQL Server 2008 Integration Services Package upgrade tool. By submitting an SSIS package, you represent that (a) you have sufficient authority and rights to submit the SSIS package(s) as provided under these Program terms and (b) you will not submit anything that includes confidential, trade secret, or otherwise proprietary information.

“Interesting” SSIS packages are those containing moderately- to highly-complex business logic.

Based on our testing of the SSIS packages, we may use the results to identify, reproduce, and file any bugs encountered against our SQL Server 2008 February Community Technology Preview (CTP) and subsequent releases (if any). Our target is to receive submissions from more than 1000 different corporate entities, each submitting at least 1 (and no more than 20) interesting SSIS package.

Benefits to you might be:

· Early knowledge about certain upgrade issues: We plan to provide an acknowledgement of receipt of the submissions, and a short filtered summary of findings from the SSIS Package upgrade testing. This may include a selection of compatibility issues encountered in the packages or SQL Server 2008. This summary is for informational purposes only and may be incomplete.

· The knowledge that your own business logic was tested as part of the Microsoft SQL Server 2008 product development process. While not a guarantee that your future upgrade will be free of issues, it provides you an additional opportunity to have Microsoft consider your business logic in its test suite.

For purpose of this Program, each unique SSIS package you choose and submit in the Program will be called a “submission.”

You will not receive any compensation of kind for submissions and there are no prizes or rewards in return for the submissions.

2.      TERM OF THE PROGRAM

This Program starts on March 21, 2008 and ends on April 14, 2008 (“Program Period”). We reserve the right to shorten or extend the Program Period depending upon when we reach our target number of participants. All rights, representations and warranties, disclaimers and limitation of liability provisions, and indemnify obligations survive any termination or expiration of this Program or your participation in this Program.

3.     CAN YOU PARTICIPATE?

You are eligible to participate in this Program if you meet the following requirements:

· You agree to and comply with these terms;

· Your enterprise has SQL Server 2005 SSIS packages running in production; and

· Your submission selects a subset of the SSIS packages running in production.

4.     WHAT IS AN ELIGIBLE SUBMISSION?

To meet the objectives of this program, a submission must meet all of the following content/technical requirements:

· The packages must represent non-trivial Extract, Transform, Load (ETL) scenarios (e.g. complex transformations on data from one or more sources into one or more destinations);

· Number of packages per entity is limited to 1-20 of the widest variety feasible; and

· The packages should be scrubbed (from the state in your production or dev/test environment) to remove all connection strings (credentials) and all other sensitive or confidential information. Packages should be resaved with encryption level = ‘Do not Save sensitive’ to remove all sensitive data. See Books Online topic on package encryption levels for more information.

Note: SQL Server Data Transformation Services (DTS) Packages are not eligible for submission in this program.

5. HOW WILL MY SUBMISSION BE POTENTIALLY USED?

We will download all SSIS package submissions sent from you (1-20 SSIS packages) onto a test server, will upgrade each package using a pre-release version of the SQL Server 2008 tool “ssisupgrade.exe”, capture any status, error or warning messages from the n packages into a single consolidated results .TXT file, produce a filtered summary of some of the typical messages in the .TXT file, into a summary .TXT file (to eliminate noise), then capture the testing results and log any bugs encountered in our bug tracking system.

We will acknowledge your submission, and send you the filtered summary report showing a selection of the most interesting or representative messages produced from your SSIS package(s) by the upgrade tool. Note: summaries may be incomplete and are provided for informational purposes only. We do not recommend or provide any fixes for the SSIS packages.

We may retain your SSIS packages indefinitely to use as real-world SSIS package examples in other internal SQL Server SSIS testing activities.

By submitting your SSIS package to us, you:

· are granting us an irrevocable, worldwide right and license, to: use, review, assess, test and otherwise analyze your SSIS package and all its content in connection with this Program;

· except where prohibited, hereby waive any and all so-called “moral rights” or any similar right that you may have or hereinafter acquire in the SSIS package and all its content, and to the extent that you can not, you hereby consent to us doing or omitting to do any act that would otherwise infringe such “moral rights” or any such similar rights;

· agree to sign any additional documentation we may require for us and our designees to make use of the rights you granted above;

· understand and acknowledge that Microsoft and other customers may have developed or commissioned materials similar or identical to your submission and you waive any claims you may have resulting from any similarities to your package submissions;

· understand that we cannot control the incoming information you will disclose to our representatives in the course of participating in this Program, or what our representatives will remember about your submission. You also understand that we will not restrict work assignments of representatives who have had access to your submission. By participating in this Program, you agree that use of information in our representatives’ unaided memories in the development or deployment of our products or services does not create liability for us under this agreement or copyright or trade secret law; and

· understand that you will not receive any compensation or credit for use of your submission.

If you do not want to grant us these rights to your SSIS package, please do not participate in this Program.

6.     HOW DO YOU SUBMIT YOUR PACKAGES?

To submit your SSIS packages, you must do all of the following during the Program Period:

· Provide: 1-20 SQL Server 2005 SSIS packages, excluding DTS packages. Each package must contain a properly formed SSIS package of moderate-to-complex complexity

· Each package can contain any SSIS components including variable, precedence constraints, event handlers, connection managers, log providers, task executables. The number of components in each package should be more than 5;

· Each package needs to be saved in a “Don’t save sensitive” mode, so no user and account authentication information will be saved in the submission package:

o Suggested steps to be performed to protect your user and account authentication information are as follows:

o Load the package in BI Designer,

o Open the package “Properties” window,

o For “ProtectionLevel” attribute, select the value “DontSaveSensitive”

o Save the package in BIDS.

o Steps to be performed to get the SSIS packages from BIDS and send it into Email:

o To locate the package from BIDS, right click the package tab and click “Open Containing Folder”, and the folder which contains the SSIS package will be opened in windows explorer.

o Locate the SSIS package file (.dtsx file) and attach it with email.

o Repeat the steps to attach more than packages with email.

o If there are any additional configuration files (.dtsconfig extension), that are used by the package, attach them in the email as well.

· Submit packages via email to ssis0803@microsoft.com

· Ensure your junk mail filter will accept any return email from the ssis0803@microsoft.com account so you don’t miss our email replies to your submission. The friendly name of this email account is “SQL Server SSIS package upgrade testing”.

If you happen to find SQL Server 2005 or 2008 product bugs in the course of preparing your submission, you are encouraged to submit those bugs via Microsoft Connect’s SQL Server site through http://connect.microsoft.com/SQLServer/Feedback.

You do not need to test SQL Server 2008 February CTP to participate in this program; submitting your SQL Server 2005 SSIS package aids us greatly by providing Microsoft a variety of test data for testing SQL Server 2008.

Your choice to participate in this program is greatly appreciated by the SQL Server 2008 development team.

7.   WHAT OTHER CONDITIONS ARE YOU ARE AGREEING TO BY PARTICIPATING IN THIS PROGRAM?

By participating in this Program you also agree:

(A)    To the extent allowable under applicable law, to release and hold harmless Microsoft its respective parents, subsidiaries, affiliates, employees and agents from any and all liability or any injury, loss, damage, right, claim or action of any kind arising from or in connection with this Program or any report result;

(B) DISCLAIMER OF WARRANTY. ANY SUMMARIES, REPORTS OR OTHER INFORMATION PROVIDED TO YOU AS A RESULT OF YOUR PARTICIPATION IN THIS PROGRAM, ARE PROVIDED TO YOU “AS IS” AND WITH ALL FAULTS. YOU BEAR THE RISK OF USING THE SUMMARIES, REPORTS AND ALL OTHER INFORMATION PROVIDED UNDER THIS PROGRAM. MICROSOFT DISCLAIMS ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTIES, DUTIES OR CONDITIONS OF OR RELATED TO: MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY OR COMPLETENESS, RESULTS, WORKMANLIKE EFFORT OR LACK OF NEGLIGENCE. ALSO THERE IS NO WARRANTY, DUTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT;

(C) LIMITATION OF LIABILITY. IN NO EVENT WILL MICROSOFT, ITS AFFILIATES OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING WITHOUT LIMITATION LOSS OF DATA, OR CONFIDENTIAL OR OTHER INFORMATION, LOST PROFITS, LOSS OF PRIVACY OR FAILURE TO MEET ANY DUTY ARISING OUT OF OR IN ANY WAY RELATED TO THIS PROGRAM EVEN IF MICROSOFT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES;

(D) THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EVEN IF ANY REMEDY FAILS ITS ESSENTIAL PURPOSE; and

(E) This Program will be governed by the laws of the State of Washington, and you consent to the exclusive jurisdiction and venue of the courts of the State of Washington for any disputes arising out of this Program.

11.   WHAT IF SOMETHING UNEXPECTED HAPPENS AND THE PROGRAM CAN’T RUN AS PLANNED?

If a virus, bug, catastrophic event, site unavailability, or any other unforeseen or unexpected event that cannot be reasonably anticipated or controlled, (also referred to as force majeure) affects the this Program, we reserve the right to cancel, change or suspend this Program. This right is reserved whether the event is due to human or technical error.

12.    PRIVACY

Microsoft’s Privacy Policy will apply to this Program and to all information that we receive from your submission. Please read the Privacy Policy before submitting your packages. Please note that by accepting these terms you are also accepting the terms of the Privacy Policy published at this location: http://privacy.microsoft.com/en-us/default.aspx.

Leave a Comment
  • Please add 1 and 3 and type the answer here:
  • Post