SQLFILE parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Automatically generated page update)
 
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Template:SQLFILE parameter subtitle}}
==Summary==
==Summary==
<dl>
<dl>
Line 10: 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&nbsp;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&nbsp;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>
Line 30: Line 32:
</ul>
</ul>
<p>With the SQLFILE parameter, <var class="product">Model&nbsp;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&nbsp;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&nbsp;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]]

Latest revision as of 12:39, 7 September 2017

SQL generated file names

Summary

Default value
0
Parameter type
System
Where set
On User 0's parameter line or reset by system manager
Related products
All
Introduced
Model 204 V4.1

Description

You can use the SQLFILE parameter to name the Model 204 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:

SettingMeaning
0 (default)Unless you specified a SYSNAME clause, your CREATE TABLE table name is taken as the name of the Model 204 file to which your table is mapped in the SQL catalog.
1Unless you specified a SYSNAME clause, Model 204 SQL processing generates a unique file name for the file to which your CREATE TABLE table is mapped in the SQL catalog.

Model 204 SQL processing maps the SQL table you name in a CREATE TABLE statement to a Model 204 file. If you do not use a SYSNAME clause, the SQL table name you use is assumed to be the name of the Model 204 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:

  • Specify the different name in a CREATE TABLE statement SYSNAME clause. Regardless of the SQLFILE setting, your SYSNAME value is the file name to which your table is mapped.
  • Have Model 204 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 Model 204 file.

With the SQLFILE parameter, Model 204 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 Mapping table names to file names.