Troubleshooting SQL Scripts - Revision history

Ollvihe: /* String Comparisons Not Being Correct */

2023-04-18T22:20:42Z

String Comparisons Not Being Correct

← Older revision		Revision as of 22:20, 18 April 2023
Line 68:		Line 68:
	Issue: Different characters are considered as similar and my analysis or script is affected.		Issue: Different characters are considered as similar and my analysis or script is affected.

	Due to the way SQL Server handles string comparisons, comparing attribute values that are in non-western character sets may result in values that are not similar to be treated as they were. For example the following characters are considered the same as the space character: Ǹ, ǹ, Ș, ș~~. This can have an effect in analyses using the attributes, i.e. Profiling Analysis, Influence Analysis, as well as Benchmarking and attribute value filtering and scripts that are run~~. To overcome this, before importing the attribute values, cast the SQL Variants holding the values into VARBINARY(MAX).		Due to the way SQL Server handles string comparisons, comparing attribute values that are in non-western character sets may result in values that are not similar to be treated as they were. For example the following characters are considered the same as the space character: Ǹ, ǹ, Ș, ș. To overcome this, before importing the attribute values, cast the SQL Variants holding the values into VARBINARY(MAX).

	For example, the following script will show characters that are treated similar as zero "0":		For example, the following script will show characters that are treated similar as zero "0":

Ollvihe: /* Client Exception When Using #ImportSapQuery Command */

2021-06-23T22:47:39Z

Client Exception When Using #ImportSapQuery Command

← Older revision		Revision as of 22:47, 23 June 2021
Line 118:		Line 118:
	(Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>		(Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

	:This issue may arise when you are extracting data from SAP and the size of 'SapWhereClauseSelect' parameter value is too large. Reduce the size of the 'SapWhereClauseSelect' value.		This issue may arise when you are extracting data from SAP and the size of 'SapWhereClauseSelect' parameter value is too large. Reduce the size of the 'SapWhereClauseSelect' value.

Ollvihe at 22:47, 23 June 2021

2021-06-23T22:47:18Z

← Older revision		Revision as of 22:47, 23 June 2021
Line 1:		Line 1:
	This page goes though some common problem situations in QPR ProcessAnalyzer scripts~~. After a script has been run, the Script Log dialog is shown. You can use it to troubleshoot your script~~.		This page goes though some common problem situations in QPR ProcessAnalyzer scripts.

	== Invalid Object Name ==		== Invalid Object Name ==

Ollvihe at 17:15, 22 June 2021

2021-06-22T17:15:40Z

Ollvihe: Ollvihe moved page Troubleshooting QPR ProcessAnalyzer Scripts to Troubleshooting SQL Scripts

2021-04-12T18:26:22Z

Ollvihe moved page Troubleshooting QPR ProcessAnalyzer Scripts to Troubleshooting SQL Scripts

← Older revision	Revision as of 18:26, 12 April 2021
(No difference)

VesKivi: /* Using "##" in a Script */

2019-02-07T09:48:22Z

Using "##" in a Script

← Older revision		Revision as of 09:48, 7 February 2019
Line 48:		Line 48:
	Issue: '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''		Issue: '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''

	This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.		This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model. Use expression like 'stringstart#' + '#stringend' or simlar to avoid have "##" in script.

	== The ? Character in Project and Model Names ==		== The ? Character in Project and Model Names ==

Ollvihe at 19:53, 2 December 2018

2018-12-02T19:53:10Z

← Older revision		Revision as of 19:53, 2 December 2018
Line 1:		Line 1:
	This page goes though some common problem situations in QPR ProcessAnalyzer scripts. After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.		This page goes though some common problem situations in QPR ProcessAnalyzer scripts. After a script has been run, the [[QPR_ProcessAnalyzer_Logs#Script_Log\|Script Log]] dialog is shown. You can use it to troubleshoot your script.

	== Invalid Object Name ==		== Invalid Object Name ==

Ollvihe: /* Client Exception When Using #ImportSapQuery Command */

2018-02-07T08:20:13Z

Client Exception When Using #ImportSapQuery Command

← Older revision		Revision as of 08:20, 7 February 2018
Line 98:		Line 98:
	Issue: Limitations in size of SAP query result.		Issue: Limitations in size of SAP query result.

	The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See [[~~Supported_QPR_ProcessAnalyzer_Commands_in_Scripts~~#--.23ImportSapQuery\|--#ImportSapQuery]] for parameter explanations.		The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See [[QPR ProcessAnalyzer Scripting Commands#--.23ImportSapQuery\|--#ImportSapQuery]] for parameter explanations.

	Issue: '''Client exception''' is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter.		Issue: '''Client exception''' is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter.

Ollvihe: /* Multiple Models with the Same Name */

2018-02-04T09:49:11Z

Multiple Models with the Same Name

← Older revision		Revision as of 09:49, 4 February 2018
Line 61:		Line 61:

	== Multiple Models with the Same Name ==		== Multiple Models with the Same Name ==
	Issue: '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''		Issue: '''There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>'''

	This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.		This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

Ollvihe: /* Multiple Projects with the Same Name */

2018-02-04T09:49:03Z

Multiple Projects with the Same Name

← Older revision		Revision as of 09:49, 4 February 2018
Line 56:		Line 56:

	== Multiple Projects with the Same Name ==		== Multiple Projects with the Same Name ==
	Issue: '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''		Issue: '''There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>'''

	This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.		This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

← Older revision		Revision as of 17:15, 22 June 2021
Line 1:		Line 1:
	This page goes though some common problem situations in QPR ProcessAnalyzer scripts. After a script has been run, the ~~[[QPR_ProcessAnalyzer_Logs#Script_Log\|~~Script Log]] dialog is shown. You can use it to troubleshoot your script.		This page goes though some common problem situations in QPR ProcessAnalyzer scripts. After a script has been run, the Script Log dialog is shown. You can use it to troubleshoot your script.

	== Invalid Object Name ==		== Invalid Object Name ==
Line 41:		Line 41:
	Issue: '''SQL error: Incorrect syntax'''		Issue: '''SQL error: Incorrect syntax'''

	You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in ~~[[Data Extraction, Transformation, and Loading#~~Supported QPR ProcessAnalyzer Commands in Scripts~~\|Supported QPR ProcessAnalyzer Commands in Scripts]]~~. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.		You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in Supported QPR ProcessAnalyzer Commands in Scripts. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

	The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.		The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.
Line 53:		Line 53:
	Issue: A project or model name contains question marks.		Issue: A project or model name contains question marks.

	The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in ~~[[Project Workspace in QPR ProcessAnalyzer Excel Client#Adding_an_Id_Column_to_the_Data_Tables_List\|~~Adding an Id Column to the Data Tables List]].		The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in Adding an Id Column to the Data Tables List.

	== Multiple Projects with the Same Name ==		== Multiple Projects with the Same Name ==
Line 98:		Line 98:
	Issue: Limitations in size of SAP query result.		Issue: Limitations in size of SAP query result.

	The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See ~~[[QPR ProcessAnalyzer Scripting Commands#--.23ImportSapQuery\|~~--#ImportSapQuery]] for parameter explanations.		The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See --#ImportSapQuery for parameter explanations.

	Issue: '''Client exception''' is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter.		Issue: '''Client exception''' is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter.