Microsoft SQL Server and Azure SQL Database Non-Spatial (JDBC) Reader Parameters
Database Connections |
---|
Connections store authentication information. For general information about sharing database connections, please seeUsing Database Connections. Note that different subsets of Database Connection parameters are made available in different contexts. ![]() Select an existing connection, orAdd Database Connectionto define a new connection. The new connection can be made visible only to the current user, or can be shared among multiple users. |
Connection Parameters
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
The host name of the Microsoft SQL Server or Azure SQL Database. (It is not necessary to specify a port if a default configuration is used.)
If you have configured your Microsoft SQL Server database to use a non-standard port number, you can specify this port here.
The correct syntax is:
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
The name of the database to connect to.
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
When connecting through a Windows user account, selectWindows Authentication. The database can validate the account name and password using the Windows principal token in the operating system.
The user account is retrieved by Windows, so if you choose Windows Authentication, theUsernameandPasswordparameters are ignored.
Select SQL Server Authentication to proceed with specifying login credentials through theUsernameandPasswordparameters.
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
When Authentication is set to SQL Server Authentication, enter the username and password to access the database.
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
Note:Note:This parameter is not present in the Azure SQL Database reader and writer. The Azure SQL Database reader and writer will always request Secure Sockets Layer (SSL) encrypted connections.
When selected, this parameter requests Secure Sockets Layer (SSL) encryption for the connection. If the server does not have a certificate trusted by the client machine, the connection will fail. Otherwise, data will be encrypted before traveling over the network. There are multiple ways to trust a server certificate on a client machine.
If this parameter is not selected, encryption behavior will be determined by encryption properties set for SQL Server Native Client, and for SQL Server.
Note:Tip:WhenEncrypt Connectionis selected, please provide a fully qualified Server name. For example, a server namedsafe-sql-servermight have a fully qualified name ofsafe-sql-server.dev.safe. This fully qualified name should be an exact match for the server name on the trusted certificate.
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
The time, in seconds, after which to terminate a query to the database if it has not yet returned a result.
If set to 0, there is no timeout. The default is 30.
Note:If this value is not set high enough, then the query will return the errorProvider Error - Timeout Expired.
Constraints
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
Enter (or browse for) the name(s) of specific database table(s) to extract.
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
This optional specification is used to limit the rows read by the reader from each table. This example selects only the features whose lengths are more than 2000:
LENGTH > 2000
Schema Attributes
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
Use this parameter to exposeFormat Attributesin Workbench when you create a workspace:
- In adynamic scenario, it means these attributes can be passed to the output dataset at runtime.
- 在一个非-dynamic scenario, you can use this parameter to expose additional attributes on multiple feature types.
Advanced
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
This parameter allows for the execution of SQL statements before opening a table for reading. For example, it may be necessary to create a temporary view before attempting to read from it.
Multiple SQL commands can be delimited by a character specified using theFME_SQL_DELIMITER
directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution.Note:Include a space before the character.
For example:
FME_SQL_DELIMITER ; DELETE FROM instructors; DELETE FROM people WHERE LastName='Doe' AND FirstName='John'
Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.
Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.
![Closed](http://www.baooytra.com/docs/fme/2017.1/html/FME_Desktop_Documentation/FME_ReadersWriters/mssql_jdbc_nonspatial/../Skins/Default/Stylesheets/Images/transparent.gif)
This parameter allows for the execution of SQL statements after a set of tables has been read. For example, it may be necessary to clean up a temporary view after creating it.
Multiple SQL commands can be delimited by a character specified using theFME_SQL_DELIMITER
directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution.Note:Include a space before the character.
For example:
FME_SQL_DELIMITER ; DELETE FROM instructors; DELETE FROM people WHERE LastName='Doe' AND FirstName='John'
Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.
Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.