Biztalk File name Macros

In a Biztalk Send port you can define the file name you are writing. Default Biztalk will use the message ID as filename (%MessageID%).
It is however possible to use a bunch of other parameters in a filename. Here 's a list of possible macros to use in the filename:

%datetime%
Coordinated Universal Time (UTC) date time in the format YYYY-MM-DDThhmmss (for example, 1997-07-12T103508).

%datetime_bts2000%
UTC date time in the format YYYYMMDDhhmmsss, where sss means seconds and milliseconds (for example, 199707121035234 means 1997/07/12, 10:35:23 and 400 milliseconds).

%datetime.tz%
Local date time plus time zone from GMT in the format YYYY-MM-DDThhmmssTZD, (for example, 1997-07-12T103508+800).

%DestinationParty%
Name of the destination party. The value comes from message the context property BTS.DestinationParty.

%DestinationPartyID%
Identifier of the destination party (GUID). The value comes from the message context property BTS.DestinationPartyID.

%DestinationPartyQualifier%
Qualifier of the destination party. The value comes from the message context property BTS.DestinationPartyQualifier.

%MessageID%
Globally unique identifier (GUID) of the message in BizTalk Server. The value comes directly from the message context property BTS.MessageID.

%SourceFileName%
Name of the file from where the File adapter read the message. The file name includes extension and excludes the file path, for example, foo.xml. When substituting this property, the File adapter extracts the file name from the absolute file path stored in the FILE.ReceivedFileName context property. If the context property does not have a value, for example, if message was received on an adapter other than File adapter, then the macro will not be substituted and will remain in the file name as is (for example, C:\Drop\%SourceFileName%).

%SourceParty%
Name of the source party from which the File adapter received the message.

%SourcePartyID%
Identifier of the source party (GUID). The value comes from the message context property BTS.SourcePartyID.

%SourcePartyQualifier%
Qualifier of the source party from which the File adapter received the message.

%time%
UTC time in the format hhmmss.

%time.tz%
Local time plus time zone from GMT in the format hhmmssTZD (for example, 124525+530).

AlwaysOn - New in SQL Server 2012

What is SQL Server AlwaysOn?

SQL Server AlwaysOn is the new high availability and disaster recovery solution for SQL Server 2012. Using AlwaysOn businesses can achieve increased application availability for their mission critical applications and get higher returns on their high availability investments through better utilization of hardware resources. AlwaysOn also increases productivity and lowers TCO by greatly simplifying high availability deployment and management.

More Info: AlwaysOn - New in SQL Server Code Name "Denali" CTP3

SQL Server 2012

The next version of SQL Server will be released in the first half of 2012.
Microsoft has confirmed this release at the PASS Summit on October 12th.
Although Microsoft was yet to announce a specific availability deadline for SQL Server 2012.
Source: SQL Server 2012 Launches in H1 2012, Now in the Final Production Stages

Microsoft already released a Developer Training kit for SQL Server 2012.
This training kit is designed to help you learn how to develop SQL Server 2012 database and BI solutions.

SQL 2012 Training Kit: SQL Server 2012 Developer Training Kit