SSIS:Best Practices - Revision history

Admin at 23:19, 18 November 2019

2019-11-18T23:19:40Z

← Older revision		Revision as of 23:19, 18 November 2019
Line 128:		Line 128:
	Although our components are tested and function on older hardware configurations, we "officially" support a recommended hardware configuration and will "unofficially" support configurations in which the components will run. Hardware configurations below the minimum requirements are not supported, in which we will advise hardware upgrades. <br>		Although our components are tested and function on older hardware configurations, we "officially" support a recommended hardware configuration and will "unofficially" support configurations in which the components will run. Hardware configurations below the minimum requirements are not supported, in which we will advise hardware upgrades. <br>

	[~~http~~:~~//www.melissadata.com/webhelp/ssis/updated/Getting_Started/Quick_Start/Quick_Start.htm#System_Requirements~~ SSIS ~~Hardware~~ Requirements]		[[SSIS:System Requirements\|SSIS System Requirements]]

Admin at 23:58, 18 December 2018

2018-12-18T23:58:38Z

← Older revision		Revision as of 23:58, 18 December 2018
Line 6:		Line 6:
	[[File:SSIS_BP_CommunityEdition.png\|link=]]		[[File:SSIS_BP_CommunityEdition.png\|link=]]

	The Community Edition of SSIS has limited functionality. Providing a few basic abilites for you to sample our products. Some options may be greyed out. If ~~Continue is choosen~~, ~~SSIS~~ will ~~switch~~ to ~~Community Edition mode and edit~~ the ~~formatted fields~~ in ~~the project~~.		The Community Edition of SSIS has limited functionality. Providing a few basic abilites for you to sample our products. Some options may be greyed out. <span style="color:red;">If you continue to run the project with a community license, the component will attempt to remove mappings not supported by the license in order to run. Please make sure to backup your configuration in order to avoid data mapping loss.</span>

	For more information on the Community Edition features, see the [[SSIS:Subscribe\|SSIS Subscribe wiki page]].		For more information on the Community Edition features, see the [[SSIS:Subscribe\|SSIS Subscribe wiki page]].

Admin at 19:24, 14 December 2018

2018-12-14T19:24:05Z

@@ Line 1: / Line 1: @@
 [[SSIS:Data Quality Components|&larr; SSIS:Data Quality Components]]
 {{CustomTOC}}
 ==Running SSIS packages from the Command Line==
 BP_XXSS_001 <br>

Oscar: /* Run on a local instance */

2015-02-09T19:09:04Z

Run on a local instance

← Older revision		Revision as of 19:09, 9 February 2015
Line 47:		Line 47:
	==Run on a local instance==		==Run on a local instance==
	BP_XXSS_005 <br>		BP_XXSS_005 <br>
	VERY IMPORTANT - We are not convinced that VM memory management can be replicated as well as a physical machine - at least not without advanced configuration on your part and high performance hardware hosting the VM - which is beyond the scope of our supporting the performance of the component. Below are some links to ~~not unrelated~~ concerns with VM performance...		VERY IMPORTANT - We are not convinced that VM memory management can be replicated as well as a physical machine - at least not without advanced configuration on your part and high performance hardware hosting the VM - which is beyond the scope of our supporting the performance of the component. Below are some links to related concerns with VM performance...

	http://www.sqlsolutions.com/articles/articles/SQL_Server_and_VMware-A_Potentially_Fatal_Combination.htm <br>		http://www.sqlsolutions.com/articles/articles/SQL_Server_and_VMware-A_Potentially_Fatal_Combination.htm <br>
Line 56:		Line 56:

	These are not meant as a deterrent, only to point out the potential issue.		These are not meant as a deterrent, only to point out the potential issue.


	==Minimum Hardware Requirements==		==Minimum Hardware Requirements==

Admin at 21:14, 7 October 2014

2014-10-07T21:14:01Z

← Older revision		Revision as of 21:14, 7 October 2014
Line 1:		Line 1:
			[[SSIS:Data Quality Components\|← SSIS:Data Quality Components]]
			{{CustomTOC}}
	==Running SSIS packages from the Command Line==		==Running SSIS packages from the Command Line==
	BP_XXSS_001 <br>		BP_XXSS_001 <br>

Admin: Admin moved page Best Practices:General SSIS to SSIS:Best Practices without leaving a redirect

2014-06-12T21:43:36Z

Admin moved page Best Practices:General SSIS to SSIS:Best Practices without leaving a redirect

← Older revision	Revision as of 21:43, 12 June 2014
(No difference)

Admin at 16:50, 23 May 2014

2014-05-23T16:50:33Z

← Older revision		Revision as of 16:50, 23 May 2014
Line 12:		Line 12:
	BP_XXSS_002 <br>		BP_XXSS_002 <br>
	We always recommend users use the most current build (version), which may contain new or improved features, code fixes, or updated functionality. Melissa data provides many ways to ensure you keep your components to the latest version.		We always recommend users use the most current build (version), which may contain new or improved features, code fixes, or updated functionality. Melissa data provides many ways to ensure you keep your components to the latest version.
	[[Best Practices:FTP and Updates\|Update details here]]		*[[Best Practices:FTP and Updates\|Update details here]]


Line 18:		Line 18:
	BP_MUXX_002 <br>		BP_MUXX_002 <br>
	Applying certain optimizations, or configuring the matchcode settings, can greatly reduce processing time without sacrificing accuracy. For a complete discussion see the Matchcodes > Optimization section of the MatchUp SSIS WebHelp or <br>		Applying certain optimizations, or configuring the matchcode settings, can greatly reduce processing time without sacrificing accuracy. For a complete discussion see the Matchcodes > Optimization section of the MatchUp SSIS WebHelp or <br>
	[[MatchUp Object:Best Practices#Optimizing Speed: Matchcodes\|Optimizing MatchUp Matchcodes]]		*[[MatchUp Object:Best Practices#Optimizing Speed: Matchcodes\|Optimizing MatchUp Matchcodes]]


Line 24:		Line 24:
	BP_MUXX_004 <br>		BP_MUXX_004 <br>
	Although the component's interface lets you change the location of the MatchUp work files, you should only override this setting after thorough testing for operating systems and speed.		Although the component's interface lets you change the location of the MatchUp work files, you should only override this setting after thorough testing for operating systems and speed.
	[[MatchUp Object:Best Practices#Keep Work File Location Local\|~~general info~~ here]]		*[[MatchUp Object:Best Practices#Keep Work File Location Local\|General Information can be found here.]]


	==MatchUp: Back up your Matchcode database==		==MatchUp: Back up your Matchcode database==
	BP_MUXX_005 <br>		BP_MUXX_005 <br>
	[[MatchUp Object:Best Practices#Back up your Matchcode database\|~~general info~~ here]]		*[[MatchUp Object:Best Practices#Back up your Matchcode database\|General Information can be found here.]]

Admin at 16:44, 23 May 2014

2014-05-23T16:44:49Z

← Older revision		Revision as of 16:44, 23 May 2014
Line 18:		Line 18:
	BP_MUXX_002 <br>		BP_MUXX_002 <br>
	Applying certain optimizations, or configuring the matchcode settings, can greatly reduce processing time without sacrificing accuracy. For a complete discussion see the Matchcodes > Optimization section of the MatchUp SSIS WebHelp or <br>		Applying certain optimizations, or configuring the matchcode settings, can greatly reduce processing time without sacrificing accuracy. For a complete discussion see the Matchcodes > Optimization section of the MatchUp SSIS WebHelp or <br>
	[[Best Practices~~:MatchUp API~~#Optimizing Speed: Matchcodes\|Optimizing MatchUp Matchcodes]]		[[MatchUp Object:Best Practices#Optimizing Speed: Matchcodes\|Optimizing MatchUp Matchcodes]]


Line 24:		Line 24:
	BP_MUXX_004 <br>		BP_MUXX_004 <br>
	Although the component's interface lets you change the location of the MatchUp work files, you should only override this setting after thorough testing for operating systems and speed.		Although the component's interface lets you change the location of the MatchUp work files, you should only override this setting after thorough testing for operating systems and speed.
	[[Best Practices~~:MatchUp API~~#Keep Work File Location Local\|general info here]]		[[MatchUp Object:Best Practices#Keep Work File Location Local\|general info here]]


	==MatchUp: Back up your Matchcode database==		==MatchUp: Back up your Matchcode database==
	BP_MUXX_005 <br>		BP_MUXX_005 <br>
	[[Best Practices~~:MatchUp API~~#Back up your Matchcode database\|general info here]]		[[MatchUp Object:Best Practices#Back up your Matchcode database\|general info here]]

Tim at 19:19, 27 February 2014

2014-02-27T19:19:21Z

← Older revision		Revision as of 19:19, 27 February 2014
Line 25:		Line 25:
	Although the component's interface lets you change the location of the MatchUp work files, you should only override this setting after thorough testing for operating systems and speed.		Although the component's interface lets you change the location of the MatchUp work files, you should only override this setting after thorough testing for operating systems and speed.
	[[Best Practices:MatchUp API#Keep Work File Location Local\|general info here]]		[[Best Practices:MatchUp API#Keep Work File Location Local\|general info here]]


			==MatchUp: Back up your Matchcode database==
			BP_MUXX_005 <br>
			[[Best Practices:MatchUp API#Back up your Matchcode database\|general info here]]

Tim at 19:55, 26 February 2014

2014-02-26T19:55:49Z

← Older revision		Revision as of 19:55, 26 February 2014
Line 18:		Line 18:
	BP_MUXX_002 <br>		BP_MUXX_002 <br>
	Applying certain optimizations, or configuring the matchcode settings, can greatly reduce processing time without sacrificing accuracy. For a complete discussion see the Matchcodes > Optimization section of the MatchUp SSIS WebHelp or <br>		Applying certain optimizations, or configuring the matchcode settings, can greatly reduce processing time without sacrificing accuracy. For a complete discussion see the Matchcodes > Optimization section of the MatchUp SSIS WebHelp or <br>
	[[Best Practices:MatchUp API#Optimizing Speed: Matchcodes\|Optimizing MatchUp ~~Speed~~]]		[[Best Practices:MatchUp API#Optimizing Speed: Matchcodes\|Optimizing MatchUp Matchcodes]]


	==MatchUp: Keep Work File Location Local==		==MatchUp: Keep Work File Location Local==