SQLBUFSZ parameter - Revision history

DCameron: /* Handling BLOBs and CLOBs */

2017-09-07T10:19:04Z

Handling BLOBs and CLOBs

← Older revision		Revision as of 10:19, 7 September 2017
Line 34:		Line 34:

	===Handling BLOBs and CLOBs===		===Handling BLOBs and CLOBs===
	When handling large objects (BLOBs and CLOBs), for performance reasons, you might want		When handling large objects ([[Field_design#BLOB.2C_CLOB.2C_and_MINLOBE_attributes\|BLOBs and CLOBs]]), for performance reasons, you might want
	to adjust the value of the SQLBUFSZ parameter to accommodate the INSERT or UPDATE of		to adjust the value of the SQLBUFSZ parameter to accommodate the INSERT or UPDATE of
	very large CLOB/BLOB columns. The SQLBUFSZ is expanded dynamically for large objects,		very large CLOB/BLOB columns. The SQLBUFSZ is expanded dynamically for large objects,

DCameron: /* Description */

2017-09-07T10:14:46Z

Description

← Older revision		Revision as of 10:14, 7 September 2017
Line 26:		Line 26:
	</table>		</table>
	<p>		<p>
	Specify <var>SQLBUFSZ</var> on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see [[Defining the user environment (CCAIN)#SQL server threads (IODEV=19)\|SQL server threads (IODEV=19)]] and [[Defining the user environment (CCAIN)#RCL thread (IODEV=49)\|RCL thread (IODEV=49)]].</p>		Specify <var>SQLBUFSZ</var> on the first <var>[[IODEV_parameter\|IODEV]]</var> 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see [[Defining the user environment (CCAIN)#SQL server threads (IODEV=19)\|SQL server threads (IODEV=19)]] and [[Defining the user environment (CCAIN)#RCL thread (IODEV=49)\|RCL thread (IODEV=49)]].</p>

	===Handling SQL statements greater than 32k bytes===		===Handling SQL statements greater than 32k bytes===

DCameron: /* Description */

2017-09-07T10:12:13Z

Description

← Older revision		Revision as of 10:12, 7 September 2017
Line 16:		Line 16:
	==Description==		==Description==
	<p>		<p>
	The size of the <var class="product">Model 204</var> [[SQL_Server_overview\|SQL Server]] buffer that assembles incoming SQL messages from a Horizon, CRAM SQL, or IUCV SQL buffer</p>		The size of the <var class="product">Model 204</var> [[SQL_Server_overview\|SQL Server]] buffer that assembles incoming SQL messages from a [[Model_204_intersystem_processing#Horizon\|Horizon]], CRAM SQL, or IUCV SQL buffer</p>
	<p>		<p>
	The <var>SQLBUFSZ</var> value defines the maximum length of an incoming SQL message. The incoming SQL message contains the SQL request in addition to the data. Since the largest incoming SQL message is likely to be a DDL transaction, set <var>SQLBUFSZ</var> large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the <var>SQLBUFSZ</var> parameter is 100000. </p>		The <var>SQLBUFSZ</var> value defines the maximum length of an incoming SQL message. The incoming SQL message contains the SQL request in addition to the data. Since the largest incoming SQL message is likely to be a DDL transaction, set <var>SQLBUFSZ</var> large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the <var>SQLBUFSZ</var> parameter is 100000. </p>

DCameron: /* Description */

2017-09-07T10:10:31Z

Description

← Older revision		Revision as of 10:10, 7 September 2017
Line 16:		Line 16:
	==Description==		==Description==
	<p>		<p>
	The size of the <var class="product">Model 204</var> SQL Server buffer that assembles incoming SQL messages from a Horizon, CRAM SQL, or IUCV SQL buffer</p>		The size of the <var class="product">Model 204</var> [[SQL_Server_overview\|SQL Server]] buffer that assembles incoming SQL messages from a Horizon, CRAM SQL, or IUCV SQL buffer</p>
	<p>		<p>
	The <var>SQLBUFSZ</var> value defines the maximum length of an incoming SQL message. The incoming SQL message contains the SQL request in addition to the data. Since the largest incoming SQL message is likely to be a DDL transaction, set <var>SQLBUFSZ</var> large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the <var>SQLBUFSZ</var> parameter is 100000. </p>		The <var>SQLBUFSZ</var> value defines the maximum length of an incoming SQL message. The incoming SQL message contains the SQL request in addition to the data. Since the largest incoming SQL message is likely to be a DDL transaction, set <var>SQLBUFSZ</var> large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the <var>SQLBUFSZ</var> parameter is 100000. </p>

DCameron: /* Summary */

2017-09-07T09:36:42Z

Summary

← Older revision		Revision as of 09:36, 7 September 2017
Line 11:		Line 11:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V6.1</var> ~~or earlier~~		<dd><var class="product">Model 204 V3.1</var>
	</dl>		</dl>

ELowell: /* Description */

2017-03-30T21:48:29Z

Description

← Older revision		Revision as of 21:48, 30 March 2017
Line 28:		Line 28:
	Specify <var>SQLBUFSZ</var> on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see [[Defining the user environment (CCAIN)#SQL server threads (IODEV=19)\|SQL server threads (IODEV=19)]] and [[Defining the user environment (CCAIN)#RCL thread (IODEV=49)\|RCL thread (IODEV=49)]].</p>		Specify <var>SQLBUFSZ</var> on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see [[Defining the user environment (CCAIN)#SQL server threads (IODEV=19)\|SQL server threads (IODEV=19)]] and [[Defining the user environment (CCAIN)#RCL thread (IODEV=49)\|RCL thread (IODEV=49)]].</p>

	====Handling SQL statements greater than 32k bytes====		===Handling SQL statements greater than 32k bytes===
	<p>		<p>
	When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set <code>SQLBUFSZ=60000</code> to run a DDL statement that is 52K.</p>		When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set <code>SQLBUFSZ=60000</code> to run a DDL statement that is 52K.</p>
	<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see [[Performance monitoring and tuning#Interpreting the SQLI and SQLO statistics\|Interpreting the SQLI and SQLO statistics]].</p>		<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see [[Performance monitoring and tuning#Interpreting the SQLI and SQLO statistics\|Interpreting the SQLI and SQLO statistics]].</p>

	====Handling BLOBs and CLOBs====		===Handling BLOBs and CLOBs===
	When handling large objects (BLOBs and CLOBs), for performance reasons, you might want		When handling large objects (BLOBs and CLOBs), for performance reasons, you might want
	to adjust the value of the SQLBUFSZ parameter to accommodate the INSERT or UPDATE of		to adjust the value of the SQLBUFSZ parameter to accommodate the INSERT or UPDATE of

ELowell: added missing BLOB section

2017-03-30T21:47:54Z

added missing BLOB section

← Older revision		Revision as of 21:47, 30 March 2017
Line 32:		Line 32:
	When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set <code>SQLBUFSZ=60000</code> to run a DDL statement that is 52K.</p>		When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set <code>SQLBUFSZ=60000</code> to run a DDL statement that is 52K.</p>
	<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see [[Performance monitoring and tuning#Interpreting the SQLI and SQLO statistics\|Interpreting the SQLI and SQLO statistics]].</p>		<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see [[Performance monitoring and tuning#Interpreting the SQLI and SQLO statistics\|Interpreting the SQLI and SQLO statistics]].</p>

			====Handling BLOBs and CLOBs====
			When handling large objects (BLOBs and CLOBs), for performance reasons, you might want
			to adjust the value of the SQLBUFSZ parameter to accommodate the INSERT or UPDATE of
			very large CLOB/BLOB columns. The SQLBUFSZ is expanded dynamically for large objects,
			based on the data that is sent. However, it is recommended that you set the value of the SQLBUFSZ parameter to the length of the average size CLOB/BLOB that is inserted or
			updated.

	[[Category:User parameters]]		[[Category:User parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

JAL: remove Sys Man guide

2014-10-30T23:50:32Z

remove Sys Man guide

← Older revision		Revision as of 23:50, 30 October 2014
Line 13:		Line 13:
	<dd><var class="product">Model 204 V6.1</var> or earlier		<dd><var class="product">Model 204 V6.1</var> or earlier
	</dl>		</dl>

	==Description==		==Description==
	<p>The size of the <var class="product">Model 204</var> SQL Server buffer that assembles incoming SQL messages from a Horizon, CRAM SQL, or IUCV SQL buffer</p>		<p>
	<p>The SQLBUFSZ value defines the maximum length of an incoming SQL message. The incoming SQL message contains the SQL request in addition to the data. Since the largest incoming SQL message is likely to be a DDL transaction, set SQLBUFSZ large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the SQLBUFSZ parameter is 100000. </p>		The size of the <var class="product">Model 204</var> SQL Server buffer that assembles incoming SQL messages from a Horizon, CRAM SQL, or IUCV SQL buffer</p>
			<p>
			The <var>SQLBUFSZ</var> value defines the maximum length of an incoming SQL message. The incoming SQL message contains the SQL request in addition to the data. Since the largest incoming SQL message is likely to be a DDL transaction, set <var>SQLBUFSZ</var> large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the <var>SQLBUFSZ</var> parameter is 100000. </p>

	<table>		<table>
	<tr><th>For...</th><th>Set SQLBUFSZ...</th></tr>		<tr class="head"><th>For...</th><th>Set SQLBUFSZ...</th></tr>

	<tr><td>A General Data Stream (GDS) passed from the conversation buffer to CMIS (SQL communications interface) receiving buffer and moved to the <var class="product">Model 204</var> SQL buffer</td><td>Greater than or equal to the maximum incoming SQL message length that can be received by the SQL server. </td></tr>		<tr><td>A General Data Stream (GDS) passed from the conversation buffer to CMIS (SQL communications interface) receiving buffer and moved to the <var class="product">Model 204</var> SQL buffer</td><td>Greater than or equal to the maximum incoming SQL message length that can be received by the SQL server. </td></tr>
	</table>		</table>
	<p>Specify SQLBUFSZ on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see the ~~<var>Rocket Model 204 System Manager's Guide~~.~~</var>~~</p>		<p>
			Specify <var>SQLBUFSZ</var> on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see [[Defining the user environment (CCAIN)#SQL server threads (IODEV=19)\|SQL server threads (IODEV=19)]] and [[Defining the user environment (CCAIN)#RCL thread (IODEV=49)\|RCL thread (IODEV=49)]].</p>

	====Handling SQL statements greater than 32k bytes====		====Handling SQL statements greater than 32k bytes====
	<p>When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set SQLBUFSZ=60000 to run a DDL statement that is 52K.</p>		<p>
	<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see the ~~<var class="book">Rocket Model 204 System Manager's Guide~~.~~</var>~~</p>		When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set <code>SQLBUFSZ=60000</code> to run a DDL statement that is 52K.</p>
			<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see [[Performance monitoring and tuning#Interpreting the SQLI and SQLO statistics\|Interpreting the SQLI and SQLO statistics]].</p>

	[[Category:User parameters]]		[[Category:User parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

ELowell at 19:14, 14 November 2013

2013-11-14T19:14:07Z

← Older revision		Revision as of 19:14, 14 November 2013
Line 18:		Line 18:
	<table>		<table>
	<tr><th>For...</th><th>Set SQLBUFSZ...</th></tr>		<tr><th>For...</th><th>Set SQLBUFSZ...</th></tr>
	<tr><~~th><var~~>A General Data Stream (GDS) passed from the conversation buffer to CMIS (SQL communications interface) receiving buffer and moved to the <var class="product">Model 204</var> SQL buffer</~~var></th~~><td>Greater than or equal to the maximum incoming SQL message length that can be received by the SQL server. </td></tr>		<tr><td>A General Data Stream (GDS) passed from the conversation buffer to CMIS (SQL communications interface) receiving buffer and moved to the <var class="product">Model 204</var> SQL buffer</td><td>Greater than or equal to the maximum incoming SQL message length that can be received by the SQL server. </td></tr>
	</table>		</table>
	~~<p><b> </b> </p>~~
	<p>Specify SQLBUFSZ on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see the <var>Rocket Model 204 System Manager's Guide.</var></p>		<p>Specify SQLBUFSZ on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see the <var>Rocket Model 204 System Manager's Guide.</var></p>
	====Handling SQL statements greater than 32k bytes====		====Handling SQL statements greater than 32k bytes====
	<p>When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set SQLBUFSZ=60000 to run a DDL statement that is 52K.</p>		<p>When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set SQLBUFSZ=60000 to run a DDL statement that is 52K.</p>
	<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see <var>Rocket Model 204 System Manager's Guide.</var></p>		<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see the <var class="book">Rocket Model 204 System Manager's Guide.</var></p>
	[[Category:User parameters]]		[[Category:User parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-08-27T16:44:03Z

Automatically generated page update

← Older revision		Revision as of 16:44, 27 August 2013
Line 1:		Line 1:
			{{Template:SQLBUFSZ parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>