SQLFILE parameter - Revision history

DCameron: /* Description */

2017-09-07T12:39:49Z

Description

← Older revision		Revision as of 12:39, 7 September 2017
Line 15:		Line 15:

	==Description==		==Description==
	<p>You can use the SQLFILE parameter to name the <var class="product">Model 204</var> file to which a CREATE TABLE table name is mapped. With SQLFILE, you can have the [[SQL_Server_overview\|SQL Server]] automatically generate a unique file name from the table name. Using a system generated file name effortlessly avoids the error of having two tables mapped to the same file.</p>		<p>You can use the SQLFILE parameter to name the <var class="product">Model 204</var> file to which a [[SQL_Data_Definition_Language_(DDL)#CREATE_TABLE_statement\|CREATE TABLE]] table name is mapped. With SQLFILE, you can have the [[SQL_Server_overview\|SQL Server]] automatically generate a unique file name from the table name. Using a system generated file name effortlessly avoids the error of having two tables mapped to the same file.</p>
	<p>The valid settings of SQLFILE are:		<p>The valid settings of SQLFILE are:
	<table>		<table>

DCameron: /* Description */

2017-09-07T12:37:58Z

Description

← Older revision		Revision as of 12:37, 7 September 2017
Line 15:		Line 15:

	==Description==		==Description==
	<p>You can use the SQLFILE parameter to name the <var class="product">Model 204</var> file to which a CREATE TABLE table name is mapped. With SQLFILE, you can have the SQL Server automatically generate a unique file name from the table name. Using a system generated file name effortlessly avoids the error of having two tables mapped to the same file.</p>		<p>You can use the SQLFILE parameter to name the <var class="product">Model 204</var> file to which a CREATE TABLE table name is mapped. With SQLFILE, you can have the [[SQL_Server_overview\|SQL Server]] automatically generate a unique file name from the table name. Using a system generated file name effortlessly avoids the error of having two tables mapped to the same file.</p>
	<p>The valid settings of SQLFILE are:		<p>The valid settings of SQLFILE are:
	<table>		<table>

DCameron: /* Summary */

2017-09-07T12:30:56Z

Summary

← Older revision		Revision as of 12:30, 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 V4.1</var>
	</dl>		</dl>

	==Description==		==Description==
	<p>You can use the SQLFILE parameter to name the <var class="product">Model 204</var> file to which a CREATE TABLE table name is mapped. With SQLFILE, you can have the SQL Server automatically generate a unique file name from the table name. Using a system generated file name effortlessly avoids the error of having two tables mapped to the same file.</p>		<p>You can use the SQLFILE parameter to name the <var class="product">Model 204</var> file to which a CREATE TABLE table name is mapped. With SQLFILE, you can have the SQL Server automatically generate a unique file name from the table name. Using a system generated file name effortlessly avoids the error of having two tables mapped to the same file.</p>

ELowell: /* Description */

2017-04-14T21:16:54Z

Description

← Older revision		Revision as of 21:16, 14 April 2017
Line 31:		Line 31:
	</ul>		</ul>
	<p>With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. </p>		<p>With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. </p>
	<p>For more information about mapping SQL tables, see ~~the <var>Model 204 SQL Server User's Guide~~. ~~</var>~~</p>		<p>For more information about mapping SQL tables, see [[SQL_Data_Definition_Language_(DDL)#Mapping_table_names_to_file_names\|Mapping table names to file names]].</p>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-08-27T16:44:04Z

Automatically generated page update

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

DmeWiccan: Automatically generated page update

2013-04-23T01:51:28Z

Automatically generated page update

← Older revision		Revision as of 01:51, 23 April 2013
Line 31:		Line 31:
	<p>With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. </p>		<p>With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. </p>
	<p>For more information about mapping SQL tables, see the <var>Model 204 SQL Server User's Guide. </var></p>		<p>For more information about mapping SQL tables, see the <var>Model 204 SQL Server User's Guide. </var></p>
	[[Category:System ~~Parameters~~]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Dme: Undo revision 56951 by DmeWiccan (talk)

2013-04-19T15:01:13Z

Undo revision 56951 by DmeWiccan (talk)

← Older revision		Revision as of 15:01, 19 April 2013
Line 31:		Line 31:
	<p>With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. </p>		<p>With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. </p>
	<p>For more information about mapping SQL tables, see the <var>Model 204 SQL Server User's Guide. </var></p>		<p>For more information about mapping SQL tables, see the <var>Model 204 SQL Server User's Guide. </var></p>
	[[Category:System ~~parameters~~]]		[[Category:System Parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-04-19T14:39:07Z

Automatically generated page update

← Older revision		Revision as of 14:39, 19 April 2013
Line 31:		Line 31:
	<p>With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. </p>		<p>With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. </p>
	<p>For more information about mapping SQL tables, see the <var>Model 204 SQL Server User's Guide. </var></p>		<p>For more information about mapping SQL tables, see the <var>Model 204 SQL Server User's Guide. </var></p>
	[[Category:System ~~Parameters~~]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Alex: Automatically generated page update

2013-02-28T00:56:57Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On User 0's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V6.1</var> or earlier
</dl>
==Description==
You can use the SQLFILE parameter to name the <var class="product">Model 204</var> file to which a CREATE TABLE table name is mapped. With SQLFILE, you can have the SQL Server automatically generate a unique file name from the table name. Using a system generated file name effortlessly avoids the error of having two tables mapped to the same file.
The valid settings of SQLFILE are:
<table>
<tr><th><var>Setting</var></th><td>Meaning</td></tr>
<tr><th><var>0 (default)</var></th><td>Unless you specified a SYSNAME clause, your CREATE TABLE table name is taken as the name of the <var class="product">Model 204</var> file to which your table is mapped in the SQL catalog.</td></tr>
<tr><th align="right"><var>1</var></th><td>Unless you specified a SYSNAME clause, <var class="product">Model 204</var> SQL processing generates a unique file name for the file to which your CREATE TABLE table is mapped in the SQL catalog.</td></tr>
</table>

<var class="product">Model 204</var> SQL processing maps the SQL table you name in a CREATE TABLE statement to a <var class="product">Model 204</var> file. If you do not use a SYSNAME clause, the SQL table name you use is assumed to be the name of the <var class="product">Model 204</var> file to which you are mapping. This is the default behavior, which corresponds to the SQLFILE setting of 0.
If you want to map your table to a file with a different name, you can do one of the following: 
<ul>
<li>
Specify the different name in a CREATE TABLE statement SYSNAME clause. <var>Regardless of the SQLFILE setting</var>, your SYSNAME value is the file name to which your table is mapped. </li>
<li>
Have <var class="product">Model 204</var> generate a unique file name for you (that is, set SQLFILE to 1). Using this setting effortlessly avoids the possibility that two tables get mapped to the same <var class="product">Model 204</var> file.</li>
</ul>
With the SQLFILE parameter, <var class="product">Model 204</var> SQL processing meets the FIPS criterion that ANSI standard SQL DDL (Data Definition Language) without implementor extensions must create the schemas necessary to run the FIPS tests. 
For more information about mapping SQL tables, see the <var>Model 204 SQL Server User's Guide. </var>
[[Category:System Parameters]]
[[Category:Parameters]]