I originally saw this as a post by Matt Masson to the SSIS Team Blog.

You can download the updated connectors here.  Here is the overview from the download page:

Overview

Microsoft Connector Version 2.0 for Oracle by Attunity – The Oracle source and destination components are written to achieve optimal performance when loading data into Oracle or unloading data from Oracle in the context of Microsoft SSIS.
Microsoft Connector Version 2.0 for Teradata by Attunity - The components are written to achieve optimal performance when loading data into Teradata or unloading data from Teradata in the context of Microsoft SSIS.
Microsoft SSIS Connectors by Attunity Version 2.0 is a minor release. It supports SQL Server 2012 Integration Services and includes bug fixes and support for updated Oracle and Teradata product releases.
The following enhancements were made:

• Oracle Enhancement – LOB Support
• Support was added for the following Oracle LOB types: CLOB, NCLOB and BLOB. These LOB types are supported by the Oracle Source component and the Oracle Destination component in array load mode.
• Oracle and Teradata Bug Fixes – Some hot key issues were fixed in the Oracle and Teradata connectors UI.
• Oracle and Teradata Bug Fixes – Localization issues were fixed in the Oracle and Teradata connectors.
• Teradata Enhancement – Support for TPT API 14.0 and TPT API 13.10.
• Support was added for Teradata 13.10 and Teradata 14.0 by supporting TPT API version 13.0 and TPT API version 14.0 (14.00.00.02 or higher). Previous versions of the TPT API are still supported.
• Teradata Enhancement – Starting from Teradata 13.0 Teradata database supports DDL with no primary index which was introduced specifically for loading data faster into Teradata; these tables were not listed in the table dropdown list.
• Teradata Bug Fix – Teradata DDL supports column names being reserved words. Teradata Connector could not work with tables having such columns.
• Teradata Bug Fix – Teradata destination component failed to read problematic rows from the error table with the following error: “Errors while trying to read error tables. Invalid TPT operator”.

Here’s the summary from the link above:

This how-to article will guide you through the process of building a Hyper-V virtual machine with Microsoft SQL Server 2012, the latest Visual Studio 2010 development tools, SQL Server Data Tools (SSDT), and an assortment of other software products to create a test environment ready for testing and product demos.

Fortunately I found the fix on a SharePoint blog.  Essentially you have add a setting to the VMWare config file.  For VMWare 7, the file is located here: C:ProgramDataVMwareVMware Workstationconfig.ini.  The setting that you need to add is mainMem.useNamedFile = “false”.  One thing to be careful of is if you copy/paste from the web, the quotes on the “false” will be curly directional style rather than the straight kind that are required for the config file.

One other setting that I changed was in the main preferences for VMWare under the Memory tab, I set the “How should the system allocate memory for virtual machines?’ to “Fit all virtual machine memory into reserved host RAM”.  I am able to do this since I have 16GB of RAM on my laptop, not sure if this is quite as feasible with less RAM.

Here’s the official description:

The Base ImageX Server is a virtual machine that can be hosted in Hyper-V that allows a user to test out the latest Business Intelligence features of SQL Server 2012 – RC0. The virtual machine has been configured to support the use of PowerView reports, PowerPivot Excel documents and various content packs allowing the user to explore the capabilities of SQL Server 2012. Working with the demos that can be installed on the ImageX server the user will have a clear picture of how the SQL Server 2012, Office and SharePoint tools support and enhance the self-service business intelligence environment.

**If you need to convert to VMWare to run on your dev machine (How come Windows 7 still  doesn’t support 64-bit VMs?), you can use VMWare vCenter Convert to convert the virtual hard disk to VMware.

Get the bits here (note, looks like you will need to compile the DLL yourself).  For now, click the link to download Change Set 86517.

**UPDATE**

Matt Masson posted the change list to the SSIS Team Blog:

Changes

• Task and Component IDs updated for SQL 2012
  • For 2005/2008 support, please use a previous version of the code
• Project upgraded to .NET 4
• EzProject – SSIS 2012 Project object model support
• Project Connection Manager support
• EzScript – Script Task support
• EzSrcDestMultiStreamPackage – new package template
• EzLookup – new TreatDuplicateKeysAsError property
• EzFileSystemTask – fixed multiple properties
• EzActiveXScript – Removed as it is no longer supported in SQL 2012

Also, it looks like this release only works against 2012.  If you need SQL 2008, you will need the older version.

(If you look in the comments, you can even find little “anonymous” nuggets, such as the following: “SQL2012 RTM is 11.0.2100.19”)

Here are the individual links/list of topics:

Restriction Operators

• Where – Simple 1
• Where – Simple 2
• Where – Simple 3
• Where – Drilldown
• Where – Indexed

Projection Operators

• Select – Simple 1
• Select – Simple 2
• Select – Transformation
• Select – Anonymous Types 1
• Select – Anonymous Types 2
• Select – Anonymous Types 3
• Select – Indexed
• Select – Filtered
• SelectMany – Compound from 1
• SelectMany – Compound from 2
• SelectMany – Compound from 3
• SelectMany – from Assignment
• SelectMany – Multiple from
• SelectMany – Indexed

Partitioning Operators

• Take – Simple
• Take – Nested
• Skip – Simple
• Skip – Nested
• TakeWhile – Simple
• TakeWhile – Indexed
• SkipWhile – Simple
• SkipWhile – Indexed

Ordering Operators

• OrderBy – Simple 1
• OrderBy – Simple 2
• OrderBy – Simple 3
• OrderBy – Comparer
• OrderByDescending – Simple 1
• OrderByDescending – Simple 2
• OrderByDescending – Comparer
• ThenBy – Simple
• ThenBy – Comparer
• ThenByDescending – Simple
• ThenByDescending – Comparer
• Reverse

Grouping Operators

• GroupBy – Simple 1
• GroupBy – Simple 2
• GroupBy – Simple 3
• GroupBy – Nested
• GroupBy – Comparer
• GroupBy – Comparer, Mapped

Set Operators

• Distinct – 1
• Distinct – 2
• Union – 1
• Union – 2
• Intersect – 1
• Intersect – 2
• Except – 1
• Except – 2

Conversion Operators

• ToArray
• ToList
• ToDictionary
• OfType

Element Operators

• First – Simple
• First – Condition
• FirstOrDefault – Simple
• FirstOrDefault – Condition
• ElementAt

Generation Operators

• Range
• Repeat

Quantifiers

• Any – Simple
• Any – Grouped
• All – Simple
• All – Grouped

Aggregate Operators

• Count – Simple
• Count – Conditional
• Count – Nested
• Count – Grouped
• Sum – Simple
• Sum – Projection
• Sum – Grouped
• Min – Simple
• Min – Projection
• Min – Grouped
• Min – Elements
• Max – Simple
• Max – Projection
• Max – Grouped
• Max – Elements
• Average – Simple
• Average – Projection
• Average – Grouped
• Aggregate – Simple
• Aggregate – Seed

Miscellaneous Operators

• Concat – 1
• Concat – 2
• EqualAll – 1
• EqualAll – 2

Custom Sequence Operators

• Combine

Query Execution

• Deferred Execution
• Immediate Execution
• Query Reuse

Join Operators

• Cross Join
• Group Join
• Cross Join with Group Join
• Left Outer Join

We are in the process of transitioning to Office 365, and one of the first features of Lync 2010 that I wanted to confirm was that Lync supported client screen scaling.  I am happy to report that it does, and it works perfectly!  To the right is a screenshot of a meeting shrunken as far as possible.  Some other very cool screen sharing features are available as well, including sharing (and scaling) multiple screens.  I have 3 screens in my development environment and I can choose to show any screen, any application running on a screen, or all 3 screens (2 are 1080p and 1 is 1600×1200 and it was not a problem).  You also can pull up a video thumbnail of what the clients are seeing, or even share a PowerPoint deck natively (not just sharing the PowerPoint app, but the .pptx file itself).  Lync 2010 is a great step forward over Live Meeting.

Sometimes your production application might require a console app.  In my case, one portion of the application I am working on will need to be implemented as a console app (for now) so that it can be executed from a SQL Server Agent job.  I want the console app to be robust and production-ready, very different from the prototype apps I cobble together in the span of a couple of minutes.

In support of a more robust console application, I found a blog post with a great template put together by Alois Kraus.  There is a blog post covering the basics, and the template can be downloaded from the Visual Studio Gallery.

At a high level, the custom console template starts you off in a Cadillac instead of a bicycle when building a console application.  Right out of the gate you get a nice command line parser, help output, color console and much more robust error handling.  I doubt I will start with the basic console template again.

As part of getting my app ready for production, I am moving the data access layer to its own project.  I started out by creating a new project in my solution and then within that project I created a new entity data model.  After that, I just added the entity model project as a reference on my sample app project.  I was missing some references, so figured out I needed to add the following using statements:

using System.Data.Objects;
using System.Data.Objects.DataClasses;

After this I was a lot closer, able to compile the app but no data was being returned.  After a bit of searching, this article helped me a ton.  The only other thing I was missing was the connection string, which I didn’t even know existed partly due to the fact that Entity Framework is so easy to get up and running via the wizard, which hides this from you.  After I copied the connection string directly from Entity Model project, I just pasted it into the <configuration> section of the App.Config of my sample app and it worked perfectly right away.

  <connectionStrings>
    <add name="MyEntities" connectionString="metadata=res://*/MyModel.csdl|res://*/MyModel.ssdl|res://*/MyModel.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=(local);initial catalog=MyDB;integrated security=True;multipleactiveresultsets=True;App=EntityFramework&quot;" providerName="System.Data.EntityClient" />
  </connectionStrings>