SSIS – C R M F o r t r e s s | Indika's Dynamics 365 CE Blog

Extensions for SSAS, SSIS and SSRS are not available for VS 2022 at this time! (Feb2022)

As per Microsoft Docs “The core SSDT functionality to create database projects has remained integral to Visual Studio. The extensions for Analysis Services, Integration Services, and Reporting Services projects are not available for Visual Studio 2022 at this time.”

Changes in SSDT for Visual Studio 2022

Data Migration to Dynamics CRM using SSIS – SS SLUG

Data migration is a vital part of a software project if it moving from one system to another. It is further important if the new system is a Microsoft Dynamics product like Microsoft Dynamics CRM.
I was able to disscuss and to have a session at Sql Server Sri Lanka User Group October meeting. Anyone can join following web site, download slides and sample codes and materials.

Download Slides and Codes:
http://www.sqlserveruniverse.com

Photos of the session from following link:
http://www.sqlserveruniverse.com/SSSLUG/Gallery/October2012.aspx

dtexec Utility (SSIS Tool)

You can run dtsx (SSIS Package) files in powershell using this tool.

EXEC xp_cmdshell ‘dtexec /f “C:\DATA\EligibilityCategory.dtsx”‘

The following example shows how to run the same package and capture the return code:

DECLARE @returncode int

EXEC @returncode = xp_cmdshell ‘dtexec /f “C:\DATA\EligibilityCategory.dtsx”‘

Following values will be returned;

Create a Credential in SQL Server Management Studio

A credential is required to connect from a outside resource to SQL Server. I needed to created a proxy to run an Integration Service and I wanted to create a credential for that.
MSDN says that a single credential can be mapped to multiple SQL Server logins and a SQL Server login can be mapped to only one credential. Only users with ALTER ANY CREDENTIAL permission can create or modify a credential.

1.In Object Explorer, expand Security, right-click Credentials, and then click New Credential.
2.In the New Credentials dialog box, in the Credential Name box, type a name for the credential.
3.In the Identity box, type the name of the account used for outgoing connections (when leaving the context of SQL Server). Typically, this will be a Windows user account. But the identity can be an account of another type.
4.In the Password and Confirm password boxes, type the password of the account specified in the Identity box. If Identity is a Windows user account, this is the Windows password. The Password can be blank, if no password is required.
5.Click OK.To create a credential