MatchUp Hub:Environment - Revision history

Admin at 17:35, 22 February 2019

2019-02-22T17:35:23Z

← Older revision		Revision as of 17:35, 22 February 2019
Line 46:		Line 46:
	:This Hot Swap CPU issue is only reported for SQL Server 2016 edition, which we may think is caused by the new cardinality estimator and automatic soft numa default features. The combination of new changes and incorrect setup in VMware may have caused the thread waits past a certain threshold.		:This Hot Swap CPU issue is only reported for SQL Server 2016 edition, which we may think is caused by the new cardinality estimator and automatic soft numa default features. The combination of new changes and incorrect setup in VMware may have caused the thread waits past a certain threshold.

	===SQL Server File Names Vs Versions===		===SQL Server File Names vs Versions===
	:{\| class="alternate01"		:{\| class="alternate01"
	!File Name!!SQL Server!!Version Number		!File Name!!SQL Server!!Version Number
Line 83:		Line 83:
	:##Select the '''Advanced''' tab		:##Select the '''Advanced''' tab
	:##Find the '''Version''' field.		:##Find the '''Version''' field.

	~~===SQL Server MatchUp Component Install Directory===~~

	:This is the Microsoft SQL Server sub directory where the SSIS installer will install the MatchUp component and processor libraries.		:This is the Microsoft SQL Server sub directory where the SSIS installer will install the MatchUp component and processor libraries.

Admin at 00:14, 19 February 2019

2019-02-19T00:14:12Z

@@ Line 14: / Line 14: @@
 ===Memory management===
-:It goes without saying that the more hardware – a faster processor, additional memory and a    fast disk drive will produce faster throughput than a lesser machine.
+:It goes without saying that the more hardware – a faster processor, additional memory and a fast disk drive will produce faster throughput than a lesser machine.
 :The MatchUp data files are loaded into memory but given their size with respect to common memory configurations, memory considerations are negligible.
@@ Line 46: / Line 46: @@
 :This Hot Swap CPU issue is only reported for SQL Server 2016 edition, which we may think is caused by the new cardinality estimator and automatic soft numa default features. The combination of new changes and incorrect setup in VMware may have caused the thread waits past a certain threshold.
-===Supported SQL, VS, and SSDT / BIDS compatibility===
+===SQL Server File Names Vs Versions===
 :Using an unsupported version may no longer produce stable processing.
@@ Line 68: / Line 112: @@
 :If one version is installed and you attempt to create a project using another version, changing your SSIS component to run in compatibility mode will not ensure that the correct library is used at runtime.
 ===64 bit installations? Running in 64 bit mode?===
@@ Line 75: / Line 128: @@
 :When processing takes place, open Task Manager – and confirm that you are running on 64 bit mode
 ===Component Option Configurations===

Admin at 14:39, 2 October 2018

2018-10-02T14:39:42Z

← Older revision		Revision as of 14:39, 2 October 2018
Line 11:		Line 11:

	===Network Speed===		===Network Speed===
	:Proprietary network configurations can vary greatly, therefore preventing us from making universal recommendations. The Best Practice is to run MatchUp as a local Installation of the application (calling program) with respect to the source data location. If your production environment requires independent application location with regard to source data, we recommend you first create local benchmarks and migrate to a production configuration -testing thoroughly along the way.		:Proprietary network configurations can vary greatly, therefore preventing us from making universal recommendations. The Best Practice is to run MatchUp as a local Installation of the application (calling program) with respect to the source data location. If your production environment requires independent application location with regard to source data, we recommend you first create local [[MatchUp Hub:Establishing Benchmarks\|benchmarks]] and migrate to a production configuration -testing thoroughly along the way.

	===Memory management===		===Memory management===

Admin at 14:31, 2 October 2018

2018-10-02T14:31:30Z

← Older revision		Revision as of 14:31, 2 October 2018
Line 38:		Line 38:
	==ETL: SSIS, Pentaho==		==ETL: SSIS, Pentaho==
	===VM===		===VM===
	:*[[FAQ:SSIS:Known Issues#SSIS VMWare: SQL Server 2016 Compatibility with ~~VMare~~\|SQL Server 2016 Compatibility with ~~VMare~~]]		:*[[FAQ:SSIS:Known Issues#SSIS VMWare: SQL Server 2016 Compatibility with VMWare\|SQL Server 2016 Compatibility with VMWare]]

	:Please avoid utilizing the option Hot Swap CPU when hosting with SQL Server 2016 with VMWare. We discovered that this is against the best practices from VMWare (3.3.6 CPU Hot Plug). Engineers from both VMware and Microsoft has verified that this will lead to issues with thread contention. The setting MAXDOP if set to too high will also have an effect on the contention and SSIS processes/our components may hang especially with our Matchup Component.		:Please avoid utilizing the option Hot Swap CPU when hosting with SQL Server 2016 with VMWare. We discovered that this is against the best practices from VMWare (3.3.6 CPU Hot Plug). Engineers from both VMware and Microsoft has verified that this will lead to issues with thread contention. The setting MAXDOP if set to too high will also have an effect on the contention and SSIS processes/our components may hang especially with our Matchup Component.

Admin at 14:18, 2 October 2018

2018-10-02T14:18:06Z

Admin at 14:13, 2 October 2018

2018-10-02T14:13:45Z

← Older revision		Revision as of 14:13, 2 October 2018
Line 1:		Line 1:
	[[MatchUp Hub\|← MatchUp Hub]]		[[MatchUp Hub\|← MatchUp Hub]]

	~~==General==~~
	==Have the Latest Build==		==Have the Latest Build==
	~~===~~Have the latest Build of the respective Melissa Data Solution.~~===~~		;Have the latest Build of the respective Melissa Data Solution.
	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.

	==Run on a Local Instance==		==Run on a Local Instance==
	===VM support===		===VM support===
	[[SSIS:Best Practices#Run on a local instance\|Run on a local instance]].		:[[SSIS:Best Practices#Run on a local instance\|Run on a local instance]].

	===Network Speed===		===Network Speed===
	Proprietary network configurations can vary greatly, therefore preventing us from making universal recommendations. The Best Practice is to run MatchUp as a local Installation of the application (calling program) with respect to the source data location. If your production environment requires independent application location with regard to source data, we recommend you first create local benchmarks and migrate to a production configuration -testing thoroughly along the way.		:Proprietary network configurations can vary greatly, therefore preventing us from making universal recommendations. The Best Practice is to run MatchUp as a local Installation of the application (calling program) with respect to the source data location. If your production environment requires independent application location with regard to source data, we recommend you first create local benchmarks and migrate to a production configuration -testing thoroughly along the way.

	===Memory management===		===Memory management===
	It goes without saying that the more hardware – a faster processor, additional memory and a fast disk drive will produce faster throughput than a lesser machine.		:It goes without saying that the more hardware – a faster processor, additional memory and a fast disk drive will produce faster throughput than a lesser machine.
	The MatchUp data files are loaded into memory but given their size with respect to common memory configurations, memory considerations are negligible.
	Your source data is not loaded into memory as a typical source database can be in the GB range.		:The MatchUp data files are loaded into memory but given their size with respect to common memory configurations, memory considerations are negligible.

			:Your source data is not loaded into memory as a typical source database can be in the GB range.

	===Process Work Files===		===Process Work Files===
	As MatchUp processes your database, it produces a matchkey for each record, sorts the keys for efficient deduping, and for some distributions, such as the ETL solutions, must keep track of source pass thru data. Using the default installation settings, these files will be located here:		:As MatchUp processes your database, it produces a matchkey for each record, sorts the keys for efficient deduping, and for some distributions, such as the ETL solutions, must keep track of source pass thru data. Using the default installation settings, these files will be located here:
	<pre>C:\Users\MyUserName\AppData\Local\Temp</pre>
	The work files are in the format of:		:<pre>C:\Users\MyUserName\AppData\Local\Temp</pre>
	<pre>myKeyFileName.key - Key File Example
			:The work files are in the format of:

			:<pre>myKeyFileName.key - Key File Example
	md29F8.002 - Temporary Sort File Example		md29F8.002 - Temporary Sort File Example
	mpAB6.tmp - Passthrough File Example</pre>		mpAB6.tmp - Passthrough File Example</pre>

	This is the temp directory of the logged in User. For *nix platforms, the directory where the executable is being ran.		:This is the temp directory of the logged in User. For *nix platforms, the directory where the executable is being ran.

	Although users can override this location, we do not recommend it, unless you are pointing this location to a fast, local drive with plenty of writable disk space and full read write permissions.		:Although users can override this location, we do not recommend it, unless you are pointing this location to a fast, local drive with plenty of writable disk space and full read write permissions.


	==ETL: SSIS, Pentaho==		==ETL: SSIS, Pentaho==
	===VM===		===VM===
	[[FAQ:SSIS:~~Knowm~~ Issues#SSIS VMWare: SQL Server 2016 Compatibility with VMare]]		:[[FAQ:SSIS:Known Issues#SSIS VMWare: SQL Server 2016 Compatibility with VMare\|SQL Server 2016 Compatibility with VMare]]

	Please avoid utilizing the option Hot Swap CPU when hosting with SQL Server 2016 with VMWare. We discovered that this is against the best practices from VMWare (3.3.6 CPU Hot Plug). Engineers from both VMware and Microsoft has verified that this will lead to issues with thread contention. The setting MAXDOP if set to too high will also have an effect on the contention and SSIS processes/our components may hang especially with our Matchup Component.		:Please avoid utilizing the option Hot Swap CPU when hosting with SQL Server 2016 with VMWare. We discovered that this is against the best practices from VMWare (3.3.6 CPU Hot Plug). Engineers from both VMware and Microsoft has verified that this will lead to issues with thread contention. The setting MAXDOP if set to too high will also have an effect on the contention and SSIS processes/our components may hang especially with our Matchup Component.

	As reported from our client, reports show that when querying SQL Server Numa in DMV (sys.dm_os_memory_nodes) only one node will be allocated 100% memory. After disabling Hot Swap CPU, SQL Server now correctly detects a single numa. Disabling Hot Swap CPU will increase performance and should prevent hanging issues from occurring in SSIS.		:As reported from our client, reports show that when querying SQL Server Numa in DMV (sys.dm_os_memory_nodes) only one node will be allocated 100% memory. After disabling Hot Swap CPU, SQL Server now correctly detects a single numa. Disabling Hot Swap CPU will increase performance and should prevent hanging issues from occurring in SSIS.

	This Hot Swap CPU issue is only reported for SQL Server 2016 edition, which we may think is caused by the new cardinality estimator and automatic soft numa default features. The combination of new changes and incorrect setup in VMware may have caused the thread waits past a certain threshold.		:This Hot Swap CPU issue is only reported for SQL Server 2016 edition, which we may think is caused by the new cardinality estimator and automatic soft numa default features. The combination of new changes and incorrect setup in VMware may have caused the thread waits past a certain threshold.

	===Supported SQL, VS, and SSDT / BIDS compatibility===		===Supported SQL, VS, and SSDT / BIDS compatibility===
	Using an unsupported version may no longer produce stable processing.		:Using an unsupported version may no longer produce stable processing.

	Melissa Data currently supports SQL Server versions 2012, 2014, 2016 and 2017. We also provide components for SQL Server 2005, 2008 and 2010 as part of the SSIS Installation, however, they are no longer supported.		:Melissa Data currently supports SQL Server versions 2012, 2014, 2016 and 2017. We also provide components for SQL Server 2005, 2008 and 2010 as part of the SSIS Installation, however, they are no longer supported.

	Certain Microsoft SQL Server version are officially supported by specific Microsoft Visual Studio versions for our components. BusinessCoder and future new component will only be offered in SSIS 2010 and newer.		:Certain Microsoft SQL Server version are officially supported by specific Microsoft Visual Studio versions for our components. BusinessCoder and future new component will only be offered in SSIS 2010 and newer.

	====Officially Supported by Melissa Data====		====Officially Supported by Melissa Data====
Line 59:		Line 63:

	===Multiple SQL installations===		===Multiple SQL installations===
	If you installed the components for one instance of SQL and are running another, you may have an older build or mismatched libraries and / or data files, which may result in sub optimal performance or component hanging.		:If you installed the components for one instance of SQL and are running another, you may have an older build or mismatched libraries and / or data files, which may result in sub optimal performance or component hanging.

	If one version is installed and you attempt to create a project using another version, changing your SSIS component to run in compatibility mode will not ensure that the correct library is used at runtime.		:If one version is installed and you attempt to create a project using another version, changing your SSIS component to run in compatibility mode will not ensure that the correct library is used at runtime.


	===64 bit installations? Running in 64 bit mode?===		===64 bit installations? Running in 64 bit mode?===
	The MatchUp processor is designed to run in 64 bit mode. Confirm that your configuration takes advantage in your project settings:		:The MatchUp processor is designed to run in 64 bit mode. Confirm that your configuration takes advantage in your project settings:
	<pre>Project> Configuration > Run64BitRuntime = True</pre>
			:<pre>Project> Configuration > Run64BitRuntime = True</pre>

	When processing takes place, open Task Manager – and confirm that you are running on 64 bit mode		:When processing takes place, open Task Manager – and confirm that you are running on 64 bit mode

	===Component Option Configurations===		===Component Option Configurations===
Line 75:		Line 80:
	*Added Lookup stream process.		*Added Lookup stream process.

	For these advanced configuration options, after the component has sorted the keys, deduped, and grouped the records, it will have to access all the cached temp file source data, and decide which columns to stream, roll-up, or use, to determine the golden record. All of which consume more processing time.		:For these advanced configuration options, after the component has sorted the keys, deduped, and grouped the records, it will have to access all the cached temp file source data, and decide which columns to stream, roll-up, or use, to determine the golden record. All of which consume more processing time.

	For source files with a large number of columns, we recommend that you configure your data source with a unique identifier and forego passing in columns that are unnecessary to the process. After processing is complete, canned ETL data tasks can easily use the unique identifier to link the Melissa Data results to the original data source record.		:For source files with a large number of columns, we recommend that you configure your data source with a unique identifier and forego passing in columns that are unnecessary to the process. After processing is complete, canned ETL data tasks can easily use the unique identifier to link the Melissa Data results to the original data source record.

	If the process requires only that all source records need to be streamed to output with a simple record disposition and group identifier, don’t configure Golden Record – the DupeGroup identifier and Result Code disposition are sufficient to query record groupings.		:If the process requires only that all source records need to be streamed to output with a simple record disposition and group identifier, don’t configure Golden Record – the DupeGroup identifier and Result Code disposition are sufficient to query record groupings.


	[[Category:MatchUp Hub]]		[[Category:MatchUp Hub]]

Admin: Created page with "← MatchUp Hub ==General== ==Have the Latest Build== ===Have the latest Build of the respective Melissa Data Solution.=== We always recommend users use th..."

2018-10-01T22:53:20Z

Created page with "← MatchUp Hub ==General== ==Have the Latest Build== ===Have the latest Build of the respective Melissa Data Solution.=== We always recommend users use th..."

New page

[[MatchUp Hub|← MatchUp Hub]]

==General==
==Have the Latest Build==
===Have the latest Build of the respective Melissa Data Solution.===
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.

==Run on a Local Instance==
===VM support===
[[SSIS:Best Practices#Run on a local instance|Run on a local instance]].

===Network Speed===
Proprietary network configurations can vary greatly, therefore preventing us from making universal recommendations. The Best Practice is to run MatchUp as a local Installation of the application (calling program) with respect to the source data location. If your production environment requires independent application location with regard to source data, we recommend you first create local benchmarks and migrate to a production configuration -testing thoroughly along the way.

===Memory management===
It goes without saying that the more hardware – a faster processor, additional memory and a fast disk drive will produce faster throughput than a lesser machine.
The MatchUp data files are loaded into memory but given their size with respect to common memory configurations, memory considerations are negligible.
Your source data is not loaded into memory as a typical source database can be in the GB range.

===Process Work Files===
As MatchUp processes your database, it produces a matchkey for each record, sorts the keys for efficient deduping, and for some distributions, such as the ETL solutions, must keep track of source pass thru data. Using the default installation settings, these files will be located here:
<pre>C:\Users\MyUserName\AppData\Local\Temp</pre>
The work files are in the format of:
<pre>myKeyFileName.key - Key File Example
md29F8.002 - Temporary Sort File Example
mpAB6.tmp - Passthrough File Example</pre>

This is the temp directory of the logged in User. For *nix platforms, the directory where the executable is being ran.

Although users can override this location, we do not recommend it, unless you are pointing this location to a fast, local drive with plenty of writable disk space and full read write permissions.

==ETL: SSIS, Pentaho==
===VM===
[[FAQ:SSIS:Knowm Issues#SSIS VMWare: SQL Server 2016 Compatibility with VMare]]

Please avoid utilizing the option Hot Swap CPU when hosting with SQL Server 2016 with VMWare. We discovered that this is against the best practices from VMWare (3.3.6 CPU Hot Plug). Engineers from both VMware and Microsoft has verified that this will lead to issues with thread contention. The setting MAXDOP if set to too high will also have an effect on the contention and SSIS processes/our components may hang especially with our Matchup Component.

As reported from our client, reports show that when querying SQL Server Numa in DMV (sys.dm_os_memory_nodes) only one node will be allocated 100% memory. After disabling Hot Swap CPU, SQL Server now correctly detects a single numa. Disabling Hot Swap CPU will increase performance and should prevent hanging issues from occurring in SSIS.

This Hot Swap CPU issue is only reported for SQL Server 2016 edition, which we may think is caused by the new cardinality estimator and automatic soft numa default features. The combination of new changes and incorrect setup in VMware may have caused the thread waits past a certain threshold.

===Supported SQL, VS, and SSDT / BIDS compatibility===
Using an unsupported version may no longer produce stable processing.

Melissa Data currently supports SQL Server versions 2012, 2014, 2016 and 2017. We also provide components for SQL Server 2005, 2008 and 2010 as part of the SSIS Installation, however, they are no longer supported.

Certain Microsoft SQL Server version are officially supported by specific Microsoft Visual Studio versions for our components. BusinessCoder and future new component will only be offered in SSIS 2010 and newer.

====Officially Supported by Melissa Data====
*Microsoft SQL Server 2017 - Microsoft Visual Studio 2017
*SQL Server Data Tools for Visual Studio 2017 - https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017#ssdt-for-vs-2017-standalone-installer
*Microsoft SQL Server 2016 - Enterprise Edition and RC2 - Microsoft Visual Studio 2015
*SQL Server Data Tools for Visual Studio 2015 (14.0.61021.0) - https://msdn.microsoft.com/en-us/mt186501.aspx?f=255&MSPPError=-2147217396
*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008 - Deprecated
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005 - Deprecated

===Multiple SQL installations===
If you installed the components for one instance of SQL and are running another, you may have an older build or mismatched libraries and / or data files, which may result in sub optimal performance or component hanging.

If one version is installed and you attempt to create a project using another version, changing your SSIS component to run in compatibility mode will not ensure that the correct library is used at runtime.

===64 bit installations? Running in 64 bit mode?===
The MatchUp processor is designed to run in 64 bit mode. Confirm that your configuration takes advantage in your project settings:
<pre>Project> Configuration > Run64BitRuntime = True</pre>

When processing takes place, open Task Manager – and confirm that you are running on 64 bit mode

===Component Option Configurations===
*Un-Needed Passthrough fields.
*Golden Record/ Survivorship used.
*Added Lookup stream process.

For these advanced configuration options, after the component has sorted the keys, deduped, and grouped the records, it will have to access all the cached temp file source data, and decide which columns to stream, roll-up, or use, to determine the golden record. All of which consume more processing time.

For source files with a large number of columns, we recommend that you configure your data source with a unique identifier and forego passing in columns that are unnecessary to the process. After processing is complete, canned ETL data tasks can easily use the unique identifier to link the Melissa Data results to the original data source record.

If the process requires only that all source records need to be streamed to output with a simple record disposition and group identifier, don’t configure Golden Record – the DupeGroup identifier and Result Code disposition are sufficient to query record groupings.

[[Category:MatchUp Hub]]

← Older revision		Revision as of 14:18, 2 October 2018
Line 4:		Line 4:
	;Have the latest Build of the respective Melissa Data Solution.		;Have the latest Build of the respective Melissa Data Solution.
	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.


	==Run on a Local Instance==		==Run on a Local Instance==
	===VM support===		===VM support===
	:[[SSIS:Best Practices#Run on a local instance\|Run on a local instance]].		:*[[SSIS:Best Practices#Run on a local instance\|Run on a local instance]].

	===Network Speed===		===Network Speed===
Line 26:		Line 27:
	:The work files are in the format of:		:The work files are in the format of:

	:<pre>myKeyFileName.key - Key File Example		<pre style="margin-left:18px;">myKeyFileName.key - Key File Example
	md29F8.002 - Temporary Sort File Example		md29F8.002 - Temporary Sort File Example
	mpAB6.tmp - Passthrough File Example</pre>		mpAB6.tmp - Passthrough File Example</pre>
Line 37:		Line 38:
	==ETL: SSIS, Pentaho==		==ETL: SSIS, Pentaho==
	===VM===		===VM===
	:[[FAQ:SSIS:Known Issues#SSIS VMWare: SQL Server 2016 Compatibility with VMare\|SQL Server 2016 Compatibility with VMare]]		:*[[FAQ:SSIS:Known Issues#SSIS VMWare: SQL Server 2016 Compatibility with VMare\|SQL Server 2016 Compatibility with VMare]]

	:Please avoid utilizing the option Hot Swap CPU when hosting with SQL Server 2016 with VMWare. We discovered that this is against the best practices from VMWare (3.3.6 CPU Hot Plug). Engineers from both VMware and Microsoft has verified that this will lead to issues with thread contention. The setting MAXDOP if set to too high will also have an effect on the contention and SSIS processes/our components may hang especially with our Matchup Component.		:Please avoid utilizing the option Hot Swap CPU when hosting with SQL Server 2016 with VMWare. We discovered that this is against the best practices from VMWare (3.3.6 CPU Hot Plug). Engineers from both VMware and Microsoft has verified that this will lead to issues with thread contention. The setting MAXDOP if set to too high will also have an effect on the contention and SSIS processes/our components may hang especially with our Matchup Component.
Line 53:		Line 54:

	====Officially Supported by Melissa Data====		====Officially Supported by Melissa Data====
	*Microsoft SQL Server 2017 - Microsoft Visual Studio 2017		:*Microsoft SQL Server 2017 - Microsoft Visual Studio 2017
	*SQL Server Data Tools for Visual Studio 2017 - https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017#ssdt-for-vs-2017-standalone-installer		:*SQL Server Data Tools for Visual Studio 2017 - https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017#ssdt-for-vs-2017-standalone-installer
	*Microsoft SQL Server 2016 - Enterprise Edition and RC2 - Microsoft Visual Studio 2015		:*Microsoft SQL Server 2016 - Enterprise Edition and RC2 - Microsoft Visual Studio 2015
	*SQL Server Data Tools for Visual Studio 2015 (14.0.61021.0) - https://msdn.microsoft.com/en-us/mt186501.aspx?f=255&MSPPError=-2147217396		:*SQL Server Data Tools for Visual Studio 2015 (14.0.61021.0) - https://msdn.microsoft.com/en-us/mt186501.aspx?f=255&MSPPError=-2147217396
	*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013		:*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
	*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012		:*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
	*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008 - Deprecated		:*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008 - Deprecated
	*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005 - Deprecated		:*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005 - Deprecated

	===Multiple SQL installations===		===Multiple SQL installations===
Line 76:		Line 77:

	===Component Option Configurations===		===Component Option Configurations===
	*Un-Needed Passthrough fields.		:*Un-Needed Passthrough fields.
	*Golden Record/ Survivorship used.		:*Golden Record/ Survivorship used.
	*Added Lookup stream process.		:*Added Lookup stream process.

	:For these advanced configuration options, after the component has sorted the keys, deduped, and grouped the records, it will have to access all the cached temp file source data, and decide which columns to stream, roll-up, or use, to determine the golden record. All of which consume more processing time.		:For these advanced configuration options, after the component has sorted the keys, deduped, and grouped the records, it will have to access all the cached temp file source data, and decide which columns to stream, roll-up, or use, to determine the golden record. All of which consume more processing time.