Uncategorized

 

SQL Server 2008 R2 Integration services (SSIS)

• Creating a simple ETL Package
  • http://msdn.microsoft.com/en-us/library/ms169917.aspx
  • Typical Uses of SSIS Packages
    • http://msdn.microsoft.com/en-us/library/ms137795.aspx
    • Package Protection Level Setting:
      • http://msdn.microsoft.com/en-us/library/ms141747.aspx
      • Running Packages:
        • http://msdn.microsoft.com/en-us/library/ms141708.aspx
        • Logging Package Execution:
          • http://msdn.microsoft.com/en-us/library/ms139845.aspx
          • Architecture of Integration Services
            • http://msdn.microsoft.com/en-us/library/bb522498.aspx
            • Architecture of an Integration Services Package
              • http://msdn.microsoft.com/en-us/library/cc645924.aspx
              • Package Deployment
                • http://msdn.microsoft.com/en-us/library/ms137592.aspx
                • Package Troubleshooting:
                  • http://msdn.microsoft.com/en-us/library/aa337088.aspx
                  • Managing Integration Services:
                    • http://msdn.microsoft.com/en-us/library/ms137731.aspx

 

References:

• Technical Reference:
  • http://msdn.microsoft.com/en-us/library/bb522642.aspx
  • Developer InfoCenter:
    • http://msdn.microsoft.com/en-us/library/ms137709.aspx
    • Integration Services Development:
      • http://msdn.microsoft.com/en-us/library/bb522537.aspx

Today I am trying to generate XSD from Well formed XML. Visual studio return this error

WFX to XSD schema generation module is not installed. Execute C:Program FilesMicrosoft BizTalk Server 2006SDKUtilitiesSchema GeneratorInstallWFX.vbs to install the WFX to XSD schema generation module.

To resolve this issue, simply run the aforementioned VB script; you’ll also need to run the InstallDTD.vbs script to add DTD support.

 

Some times run installWFX.vbs does not solve the problem then do one more step copy dll inside

“C:Program FilesMicrosoft BizTalk Server 2006SDKUtilitiesSchema Generator” to  folder “C:Program Files (x86)Microsoft BizTalk Server 2010Developer ToolsSchema Editor Extensions”

It will solve the problem

For starting Date

int month = DateTime.Now.Month;
int year = DateTime.Now.Year;

// if month is october or later, the FY started 10-1 of this year
// else it started 10-1 of last year
return month > 9 ? new DateTime( year, 10, 1 ) : new DateTime( year - 1, 10, 1 );

For Ending Date

// get the current month and year
int month = DateTime.Now.Month;
int year = DateTime.Now.Year;

// if month is october or later, the FY ends 9/30 next year
// else it ends 9-30 of this year
return month > 9 ? new DateTime( year + 1, 9, 30 ) : new DateTime( year, 9, 30 );

i used following Expression in  Integer values expression shap

 

(DT_WSTR, 4) YEAR( @[User::StartDate]  )  +
Right("0"+ (DT_WSTR, 2) MONTH( @[User::StartDate] ) ,2) +
Right("0"+ (DT_WSTR, 2) DAY( @[User::StartDate]  ) ,2)

It convert the date into integer like  20120229

Cumulative update package 4 for BizTalk Server 2010 is now available and it is a rollup update that contains the following items:

• All previously released hotfixes for BizTalk Server 2010
• Some hotfixes for Microsoft BizTalk Server 2009 and for Microsoft BizTalk Server 2006 R2
• Some other fixes that improve the product

This cumulative update package for Microsoft BizTalk Server 2010 contains hotfixes for the BizTalk Server 2010 issues that were resolved after the release of BizTalk Server 2010.

Hotfixes that are included in cumulative update package 4 for BizTalk Server 2010

BizTalk Server EDI support

• 2642402: FIX: An EDI pipeline does not work after you install BizTalk Server 2010 CU1 or BizTalk Server 2010 CU2
• 2662496: FIX: Incorrect outbound messages if the Envelopes default transaction type is not set to the HIPAA 277_A message in BizTalk Server 2010
• 2662536: FIX: Invalid value for the AK301 segment when you receive an EDI message that has a bad segment identifier in BizTalk Server 2010

BizTalk Server Message Runtime and Pipelines

• 2672494: FIX: The BizTalk Server MessageBox database grows very large because records are not cleared in the EqualsPredicate2ndPass table in BizTalk Server 2010
• 2662532: FIX: A “Backup BizTalk Server (BizTalkMgmtDb)” job on BizTalk Server 2010 fails when you try to back up a custom database

Collapse this tableExpand this tableBizTalk Server Management Tools

• 2673264: FIX: “Error saving map. Stored procedure returned non-zero result.” error message when you deploy the BizTalk Server 2010 applications in BizTalk Server 2010 Administration Console
• 2672496: FIX: A 64-bit application that uses the Microsoft.BizTalk.ExplorerOM.dll file fails if the BizTalk Management Database is on a named instance in BizTalk Server 2010

Note: It is recommended that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included in the previous BizTalk Server 2010 update release. However, it is recommended that you consider applying the most recent BizTalk Server 2010 update release.

To know more about this CU check Microsoft Help and Support.

Original post by Guru Venkataraman (BizTalk Customer Response Team) here