Customization Suite - ODBC

Transcription

1 Customization Suite - ODBC

2

3 Notice of Copyright Published by Maximizer Software Inc. Copyright All rights reserved. Registered Trademarks and Proprietary Names Product names mentioned in this document may be trademarks or registered trademarks of Maximizer Software Inc. or other hardware, software, or service providers and are used herein for identification purposes only. Applicability This document applies to Maximizer CRM 10.5 and Maximizer CRM 10.5 Customization Suite software.

4 Maximizer Software Address Information Corporate Headquarters Americas Maximizer Software Inc West Pender Street 10th Floor Vancouver, BC, Canada V6E 2N phone fax support Knowledge Base: Europe, Middle East, and Africa Maximizer Software Ltd 2nd Floor - Apex House, London Road Bracknell, Berkshire RG12 2XH United Kingdom phone fax info@maximizer.co.uk Asia Maximizer Asia Limited 17/F, Regent Centre 88 Queen's Road Central, Hong Kong +(852) phone +(852) fax info@maximizer.com.hk Australia Maximizer Software Solutions Pty. Ltd. Level 10, 815 Pacific Highway Chatswood, New South Wales Australia, (0) phone +61 (0) fax info@maximizer.com.au

5 i Contents Chapter 1 Introduction...1 Who Should Use This Guide?...2 Related Documentation...2 Chapter 2 Maximizer ODBC: Overview...5 Using Maximizer ODBC...7 Defining a Data Source...8 Using ODBC-Compliant Software...9 Access Control and Security...10 Database Level...10 Table Level...10 Record Level...11 Field Level...11 Chapter 3 Maximizer ODBC: Programmer s...13 Maximizer ODBC Limits...14 ODBC API Conformance...15 Notes on the ODBC API Conformance Table...17 SQLMoreResults...17 SQLTransact...17 SQLSetStmtOption / SQLGetStmtOption...17 SQLSetConnectOption / SQLGetConnectOption...18 SQLGetTypeInfo...18 SQLGetInfo...18 SQLSpecialColumns...23 SQL Conformance...24 Minimum SQL Grammar...24 Core SQL Grammar...25 Extended SQL Grammar...27 Delimited Identifiers in SQL Statements...29 Scalar Functions...30 String Functions...30 Numeric Functions...30 Date Functions...30 System Functions...30 Conversion Functions...31 Data Types...32

6 ii Maximizer CRM 10.5 ODBC Data Type Mapping...32 Limitations on SQL_LONGVARCHAR...33 Comparison of Floats...33 Representation of Float Infinity...34 Maximizer Date and Time...34 Other Characteristics...35 SQL Statement Limitations...35 Stack Size...35 Precision and Scale...35 Collate Sequence...35 Closing an Open Table...36 Concurrency...36 Extensions to the ODBC GROUP BY Syntax...37 GROUP BY Syntax...37 GROUP BY Semantics...37 SELECT Statement select-list...37 HAVING With GROUP BY...38 Left Outer Join...39 Syntax...39 Vendor Strings...39 Examples of Left Outer Join...40 Tips and Tricks for Maximizer ODBC...44 Joining...44 Selecting...44 Updating...44 General Tips...44 Examples of Inserting Records Using Maximizer ODBC...45 Chapter 4 Maximizer ODBC: Data Tables...47 Alphabetical List of Maximizer ODBC Tables...48 Common Fields...50 Identity Fields...50 Security Fields...50 History Fields...51 User-Defined Field Tables...53 About User-Defined Field Tables...53 User-Defined Field Type_Id Constants...54 UDF_List Table...56 UDF_Table_Item Table...61 Combined_Client_User_Fields Table...63 Address Book Entry Tables...64 ABPartners Table...65 Address Table...66 Client Table...68 Company Table...74 People Table...77

7 iii Related_Entries Table...82 Appointment, Hotlist, and Notes Tables...85 Appointments Table...85 Hotlist Table...90 Notes Table...93 Campaign Tables...97 Automatic_Campaign Table...98 CampaignAccounts Table Combined_Campaign_User_Fields Table Manual_Campaign Table Customer Service Tables Combined_CSCase_User_Fields Table CSCases Table Opportunity Tables Activity Table Combined_Opp_User_Fields Table Currency Table OppActivity Table OppComp Table OppContact Table Opportunity Table OppPartners Table OppRole Table OppStep Table OppSuccessFactor Table Prob_Close_Range Table Reasons Table Strategy Library Tables Role Table Role_Standing_Link Table Standing_For_Role Table Standing_For_Success_Factor Table Step Table Step_Activity_Link Table Strategy Table Strategy_Role_Link Table Strategy_Success_Factor_Link Table Strategy_Step_Link Table Success_Factor Table Success_Factor_Standing_Link Table User and Group Tables Security_Group Table Team Table User_Details Table Third-Party Synchronization Tables Custom_Independent Table...168

8 iv Maximizer CRM 10.5 Custom_Child Table Index...179

9 1 C HAPTER 1Introduction In this chapter... Who Should Use This Guide? on page 2 Related Documentation on page 2

10 2 Maximizer CRM 10.5 This guide explains how to use ODBC in the Maximizer environment. It is a reference to the Maximizer database structure. It describes security that the Maximizer ODBC provides at the database, table, record, and field level. In addition the section shows the relationships between Maximizer data tables. It also describes each Maximizer data table, the fields within each table and the table indexes. Who Should Use This Guide? This guide is intended for business partners (value-added resellers) and developers. Related Documentation The Maximizer Customization Suites include the following guides. Accounting Link API Guide DDE API Guide ODBC Data Tables Guide Volume I Guide Volume II Guide Payment Gateway Architecture Guide When the Customization Suite is installed, these guides are available in PDF from the Maximizer Customization Suite folder in the Windows Start menu. The following additional documentation resources are available for Maximizer Enterprise: Online help (Help > Contents) provides additional information about using Maximizer and Administrator. Context-sensitive help (F1) provides details specific to the screen currently active in Maximizer. Press the F1 key to activate context-sensitive help for the current screen. The Maximizer Enterprise User s Guide is your reference guide to using Maximizer. This guide is available in PDF format from the Help menu in Maximizer and Administrator. The Maximizer Enterprise Administrator s Guide is your reference to installing, configuring, and managing Maximizer Enterprise. This guide is available in PDF format from the Help menu in Maximizer and Administrator The Maximizer Accounting Link User s Guide is your reference guide to configuring and using the Maximizer Accounting Link Designed for Use with QuickBooks. This guide is available in PDF format from the Help menu in Maximizer and Administrator. The MaxExchange Administrator s Guide is your reference guide to configuring and using MaxExchange. This guide is available in PDF format from

11 Chapter 1 3 the Maximizer Enterprise folder in the Windows Start menu when MaxExchange Synchronization Server is installed. The Maximizer Enterprise Training Guide includes detailed instructions and step-by-step exercises designed for classroom training or self-instruction. The Maximizer website ( provides the latest product information. It also includes a searchable Knowledge Base at

12 4 Maximizer CRM 10.5

13 2 C HAPTER 2Maximizer ODBC: Overview In this chapter... Using Maximizer ODBC on page 7 Access Control and Security on page 10

14 6 Maximizer CRM 10.5 Open Database Connectivity (ODBC) is an open programming interface that you can use to access data that is stored on database management systems (DBMS). Maximizer ODBC is a translator that allows you to read and write Maximizer data from ODBC-compliant applications. It also lets you access Maximizer databases for reporting and analysis. Typical applications you can use for these purposes include spreadsheets (for example, Excel and Lotus 1-2-3), report writers (for example, Crystal Reports and Impromptu), and executive information systems. On the basis of its read/write capabilities alone, the ODBC Driver extends the reach of your other applications and increases the usability and value of your Maximizer data. But the Maximizer ODBC Driver is much more than a basic driver. To begin, it uses validation rules to ensure the integrity of your Maximizer data which is beyond the scope of a basic ODBC driver. It also provides excellent security at the database, table, record, and field levels to ensure that access to data is tightly controlled according to assigned user rights. In addition, the Customization Suite Guides describe the structure and contents of each Maximizer data table, illustrate the links between tables, provide tips for efficient use of the driver, and contain a thorough programmer s reference. They enable you to optimize your use of the driver and save valuable development time.

15 Chapter 2 7 Using Maximizer ODBC Now that you have installed the driver, you are almost ready to access the data contained in Maximizer databases. Before you can do this, however, you must know how to define a data source. By defining a data source, you create a link between Maximizer and a database that you have selected. And since you are going to open Maximizer s database from within another application, you must also consult the user s guide that comes with that third-party application to determine how to use the program to access the ODBC database. When using ODBC with Address Books that do not have security enabled, you may optionally set the system login registry key as instructed below to suppress the login dialog box. This process should be used only for Address Book folders that do not have security enabled doing otherwise may result in ODBC connection errors. To set the registry key for Address Books not using security Open the Windows Registry Editor. The Registry Editor is an advanced tool that enables you to change settings in your system Registry. To do this: Click the Windows Start button to display the Start menu. Select Run, type REGEDIT and click OK. Go to the branch: HKEY_LOCAL_MACHINE\Software\ODBC\ODBCINST.INI\Maximizer ODBC Driver. Select New > String Value and enter SystemLogin. Double-click on the string and enter the value of False. This suppresses the default Maximizer ODBC login dialog box.

16 8 Maximizer CRM 10.5 Defining a Data Source A data source is the connection you make between the Maximizer ODBC Driver and a Maximizer database. You need to establish a connection in order to access the data in a given Maximizer database. You must define a data source for each database you want to access. Once you have defined a data source, however, the link between the Maximizer ODBC Driver and that database is permanent. To define a data source Open Data Sources (ODBC) from the Administrative Tools menu. You can access Administrative Tools through either the Control Panel or the Windows Start menu. The ODBC Data Source Administrator window appears. Click the System DSN tab. Click the Add button. The Create New Data Source window appears. Select Maximizer ODBC Driver and click Finish. The ODBC Maximizer Driver Setup window appears. From the drop-down list, select the name of the Maximizer database you want to access. Click the Options>> button, and select the following options as required: UDF Table Items Separation Char: Defines the character used to separate the UDF table item TRUE Date: With the default setting not checked, Maximizer date/time field information is retrieved as a String data type. However, if the TRUE Date option is checked, then Maximizer returns date/time fields as Date data type. The format for both the String and Date data types is determined by the short Date style and by the Date separator setting, set into the regional setting. UDF Tables Shown: With the default setting checked, Maximizer ODBC will include all UDF Tables in a Table Def type record set. If the UDF Tables Shown option is not selected, then all UDF Tables are not available through Maximizer ODBC. MR_MS: With the default setting not checked, the Mister/Miss field name appears as MR/MS. For systems that don't accept the '/' as a valid character for a field name, check the MR_MS options to have the Mister/Miss field name appear as MR_MS." Close the Maximizer ODBC Driver Setup dialog box and the ODBC Data Source Administrator.

17 Chapter 2 9 Using ODBC-Compliant Software You are now ready to use ODBC-compliant applications to access data stored in Maximizer databases. However, each ODBC-compliant application has its own set of commands for using an ODBC driver. Therefore, you need to consult the user s guide for the third-party application you are using for information about how to access data in an external relational database through an ODBC driver. Note You must enter a User ID to access Maximizer s ODBC database even if Maximizer security is not enabled. The default User ID is MASTER; the default password is CONTROL. If Maximizer security is enabled, then enter your User ID as you normally would in Maximizer. Note When linking to an external data source in Microsoft Access, you must specify a field or combination of fields as a unique index for each linked table. For the majority of tables, you can use the Data_Machine_Id and Sequence_Number fields as the unique index fields when linking to Maximizer ODBC driver data tables from Microsoft Access. The Team table is one exception because you must specify the first four fields as unique index fields: Db_Id, Rec_Type, Team_Id, and Team_Member_Id. The Maximizer ODBC Driver Data Tables chapter includes a list of index definitions for each table, and you can use any of the unique indexes to link to the tables from Microsoft Access.

18 10 Maximizer CRM 10.5 Access Control and Security The Maximizer ODBC Driver uses the same access control that is set up in Maximizer s Security tab, which is accessible from File > Preferences in Maximizer. The security is implemented at four levels: database level table level record level field level Each of these levels are described in this chapter. To access the Maximizer ODBC Driver Database Level Table Level Select Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). Click the Add button. Select Maximizer ODBC Driver from the list, and click Finish. Select the Address Book to use as a data source, and click OK. the list of databases available to Maximizer is present when ODBC data sources are being set up. To gain access to the data source, the user must log in as a valid Maximizer user and supply the correct password. those tables that are set to be readable in Maximizer are visible to the user. If the user has no Read rights, then a table cannot be attached or opened.

19 Chapter 2 11 Record Level Depending on the access rights of the Maximizer user, only certain records are returned. For example, no private Address Book entries and associated tasks and appointments are shown if the Open other user s private entries checkbox is not selected in the Maximizer s Security Tab. The user can see OppActivity, OppStep, OppSuccessFactor, OppRole, and OppComp records only if they are a team member of an Opportunity. Also, only the Opportunity leader can delete an Opportunity record once it has been created. Note Master has access to all non-system records and fields. Field Level Certain fields may be protected depending on the user or group rights. For example, a user who is not a team member of an opportunity cannot modify the opportunity s Objective field.

20 12 Maximizer CRM 10.5

21 3 C HAPTER 3Maximizer ODBC: Programmer s In this chapter... Maximizer ODBC Limits on page 14 ODBC API Conformance on page 15 Notes on the ODBC API Conformance Table on page 17 SQL Conformance on page 24 Scalar Functions on page 30 Data Types on page 32 Other Characteristics on page 35 Extensions to the ODBC GROUP BY Syntax on page 37 Left Outer Join on page 39 Tips and Tricks for Maximizer ODBC on page 44

22 14 Maximizer CRM 10.5 The material in this chapter describes the characteristics of the Maximizer ODBC Driver, including operating system platforms supported by the Maximizer ODBC summary of Maximizer ODBC limits ODBC API conformance of the Maximizer ODBC to ODBC API SQL conformance of the Maximizer ODBC scalar functions supported by the Maximizer ODBC data types supported by the Maximizer ODBC other characteristics of the Maximizer ODBC For detailed information on the ODBC API, SQL grammar, scalar functions, and SQL data types, see Microsoft s ODBC 2.0 Programmer s and SDK Guide. Maximizer ODBC operates on Windows 95, Windows 98, Window NT 4.0, and Windows Maximizer ODBC Limits The following limits apply to Maximizer ODBC: Number of rows: 2 billion Number of columns in a query: 255 Size of a column: 2 gigabytes Number of connections: limited by memory Number of statements per connection: limited by memory Table name length: 64 characters Column name length: 64 characters Database qualifier: 68 characters Number of joined tables: limited by memory

23 Chapter 3 15 ODBC API Conformance Maximizer ODBC conforms to the ODBC Level 1 API. The following table lists the ODBC API functions that Maximizer ODBC supports. Table 1 ODBC API Functions Supported by Maximizer ODBC Function Conformance Level SQLAllocEnv Core SQLAllocEnv Core SQLAllocStmt Core SQLBindCol Core SQLCancel Core SQLColAttributes Core SQLColumns Level 1 SQLConnect Core SQLDataSources Level 2 SQLDescribeCol Core SQLDisconnect Core SQLDriverConnect Level 1 SQLError Core SQLExecDirect Core SQLExecute Core SQLFetch Core SQLFreeConnect Core SQLFreeEnv Core SQLFreeStmt Core SQLGetConnectOption Level 1 SQLGetCursorName Core SQLGetData Level 1 SQLGetFunctions Level 1 SQLGetInfo Level 1 SQLGetStmtOption Level 1 SQLGetTypeInfo Level 1

24 16 Maximizer CRM 10.5 Table 1 ODBC API Functions Supported by Maximizer (Continued) ODBC Function Conformance Level SQLMoreResults Level 2 SQLNumResultCols Core SQLParamData Level 1 SQLPrepare Core SQLPutData Level 1 SQLRowCount Core SQLSetConnectOption Level 1 SQLSetCursorName Core SQLSetParam Core SQLSetStmtOption Level 1 SQLSpecialColumns Level 1 SQLStatistics Level 1 SQLTables Level 1 SQLTransact Core

25 Chapter 3 17 Notes on the ODBC API Conformance Table SQLMoreResults SQLTransact Maximizer ODBC always returns SQL_NO_DATA_FOUND for this function. (Maximizer ODBC supports this function, with its return value, because of Microsoft Access requirements.) Maximizer ODBC does not support transactions or ROLLBACK. It supports AUTOCOMMIT in that all data written is committed automatically. SQLTransact always returns SQL_SUCCESS when ftype is SQL_COMMIT and always returns SQL_ERROR when ftype is SQL_ROLLBACK. SQLSetStmtOption / SQLGetStmtOption The following table describes the options that Maximizer ODBC supports for SQLSetStmtOption and SQLGetStmtOption. Table 2 Option Supported for SQLSetStmtOption / SQLGetStmtOption foption vparam Comments SQL-MAX-LENGTH SQL-NOSCAN SQL-MAX-ROWS See Microsoft s ODBC SDK Programmer s. See Microsoft s ODBC SDK Programmer s. See Microsoft s ODBC SDK Programmer s.

26 18 Maximizer CRM 10.5 SQLSetConnectOption / SQLGetConnectOption The following table describes the options that Maximizer ODBC supports for SQLSetConnectOption and SQLGetConnectOption. Table 3 Option Supported for SQLSetConnectOption / SQL GetConnectOption foption vparam Comments SQL-ACCESS-MODE SQL_AUTOCOMMIT SQL_CURRENT_QUALIFIER (65000) See Microsoft s ODBC SDK Programmer s. Valid with SQLGetConnectOption but not valid with SQLSetConnectOption since SQL_AUTOCOMMIT is always on. Valid with SQLGetConnectOption. Returns the current table qualifier. To set a table qualifier, use the USE statement. SQLGetTypeInfo SQLGetInfo SQLGetTypeInfo generates a list of database-specific data type names ( TYPE_NAME ) specified by Maximizer ODBC. The following table lists the values returned by Maximizer ODBC for the SQLGetInfo options. Table 4 Values Returned for SQLGetInfo Options finfotype SQL_ACCESSIBLE_PROCEDURES SQL_ACCESSIBLE_TABLES SQL_ACTIVE_CONNECTIONS SQL_ACTIVE_STATEMENTS SQL_CONCAT_NULL_BEHAVIOR SQL_CONVERT_BIGINT SQL_CONVERT_BINARY Return Values N for No. N for No. 0 to indicate no limit. 0 to indicate no limit. 1 to indicate that the result is a concatenation of non-null valued columns. 0 for conversion not supported. 0 for conversion not supported.

27 Chapter 3 19 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_CONVERT_BIT SQL_CONVERT_CHAR SQL_CONVERT_DATE SQL_CONVERT_DECIMAL SQL_CONVERT_DOUBLE SQL_CONVERT_FLOAT SQL_CONVERT_FUNCTIONS SQL_CONVERT_INTEGER SQL_CONVERT_LONGVARBINAR Y Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. 1 for conversion supported. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. 0 for conversion not supported.

28 20 Maximizer CRM 10.5 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_CONVERT_LONGVARCHAR SQL_CONVERT_NUMERIC SQL_CONVERT_REAL SQL_CONVERT_SMALLINT SQL_CONVERT_TIME SQL_CONVERT_TIMESTAMP SQL_CONVERT_TINYINT SQL_CONVERT_VARBINARY SQL_CONVERT_VARCHAR Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. 0 for conversion not supported. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide.

29 Chapter 3 21 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_CORRELATION_NAME (65000) SQL_CURSOR_COMMIT_ BEHAVIOR SQL_CURSOR_ROLLBACK_ BEHAVIOR SQL_DATA_SOURCE_NAME SQL_DATA_SOURCE_READ_ONL Y SQL_DATABASE_NAME SQL_DBMS_NAME SQL_DBMS_VER SQL_DEFAULT_TXN_ISOLATION SQL_Driver_HDBC SQL_Driver_HENV SQL_Driver_HSTMT SQL_Driver_NAME SQL_Driver_VER SQL_EXPRESSIONS_IN_ORDERBY SQL_FETCH_DIRECTION SQL_FILE_USAGE (65002) 2 to indicate that any correlation name can be used. 2 to indicate that cursors are preserved in the same position as before the COMMIT operation and that the application can execute or fetch without preparing the statement again. 0 to indicate that cursors are closed and deleted and that the application must prepare and execute the next statement. Long pointer to the name of the underlying data source. N for No. Long pointer to the current table qualifier. Long pointer to the DBMS name character string supplied by Maximizer ODBC (e.g., MAXWIN ). Long pointer to the version character string supplied by Maximizer ODBC (e.g., 1.20 ). 0 to indicate that transactions are not supported. Handled by the Driver Manager (ODBC.DLL). Handled by the Driver Manager (ODBC.DLL). Handled by the Driver Manager (ODBC.DLL). Long pointer to the name of Maximizer ODBC. Long pointer to the version of Maximizer ODBC in the form nn.nn.nnnn (e.g., ). Y for Yes. SQL_FD_FETCH_NEXT. The returned value is a 16-bit integer that indicates how the driver directly treats files in a data source. A value of 0 (SQL_FILE_NOT_SUPPORTED) indicates that the driver is not a single-tier driver. A value of 1 (SQL_FILE_TABLE) indicates a single-tier driver that treats files in a data source as tables. A value of 3 (SQL_FILE_QUALIFIER) indicates a single-tier driver that treats files in a data source as a qualifier.

30 22 Maximizer CRM 10.5 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_IDENTIFIER_CASE 4 to indicate that identifiers are mixed case (i.e., not case sensitive). SQL_IDENTIFIER_QUOTE_CHAR Long pointer to the double-quote character ( ). SQL_MAX_COLUMN_NAME_LEN 64. SQL_MAX_CURSOR_NAME_LEN 18. SQL_MAX_OWNER_NAME_LEN SQL_MAX_PROCEDURE_NAME_ LEN SQL_MAX_QUALIFIER_NAME_LE N 0 to specify that owner names are not supported. 0 to specify that procedure names are not supported. 68. SQL_MAX_TABLE_NAME_LEN 64. SQL_MULT_RESULT_SETS SQL_MULTIPLE_ACTIVE_TXN SQL_NUMERIC_FUNCTIONS SQL_NON_NULLABLE_COLUMNS (65001) SQL_ODBC_API_CONFORMANCE SQL_ODBC_SAG_CLI_ CONFORMANCE SQL_ODBC_SQL_CONFORMANC E SQL_ODBC_SQL_OPT_IEF SQL_ODBC_VER SQL_OUTER_JOINS SQL_OWNER_TERM SQL_PROCEDURE_TERM SQL_PROCEDURES SQL_QUALIFIER_NAME_ SEPARATOR SQL_QUALIFIER_TERM N for No. N for No. SQL_FN_NUM_MOD. 1 (SQL_NNC_NON_NULL) to indicate that NOT NULL is enforced in CREATE TABLE statements. 0 (SQL_NNC_NULL) to indicate that NOT NULL is not enforced in CREATE TABLE statements. 1 for Level 1 conformance. 1 for SAG-compliant. 0 to indicate Minimum SQL conformance, although Maximizer ODBC supports some core SQL functions as well. N for No. Handled by the Driver Manager (ODBC.DLL). Y for Yes. to indicate not supported by this driver. to indicate not supported by this driver. N for No. \. DATABASE.

31 Chapter 3 23 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_ROW_UPDATES SQL_SCROLL_CONCURRENCY SQL_SCROLL_OPTIONS SQL_SEARCH_PATTERN_ESCAPE \. SQL_SERVER_NAME Y for Yes. SQL_SCCO_READ_ONLY. SQL_SO_FORWARD_ONLY. Long pointer to the server name character string supplied by Maximizer ODBC (e.g., MAXIMIZER ). SQL_STRING_FUNCTIONS SQL_FN_STR_CONCAT SQL_FN_STR_LEFT SQL_FN_STR_LTRIM SQL_FN_STR_LENGTH SQL_FN_STR_LCASE SQL_FN_STR_RIGHT SQL_FN_STR_RTRIM SQL_FN_STR_SUBSTRING SQL_FN_STR_UCASE. SQL_SYSTEM_FUNCTIONS SQL_TABLE_TERM SQL_FN_SYS_USERNAME SQL_FN_SYS_DBNAME. TABLE. SQL_TIMEDATE_FUNCTIONS SQL_FN_TD_CURDATE SQL_FN_TD_DAYOFMONTH SQL_FN_TD_DAYOFWEEK SQL_FN_TD_MONTH SQL_FN_TD_YEAR SQL_FN_TD_CURTIME. SQL_TXN_CAPABLE SQL_TXN_ISOLATION_OPTION SQL_USER_NAME 0 to indicate that transactions are not supported. 0 to indicate that transactions are not supported. Character string of the login name. SQLSpecialColumns Maximizer ODBC uses unique indexes as the optimal set of columns that uniquely identify a row in the table. Maximizer ODBC cannot identify columns that are automatically updated when any value in the row is updated by a transaction.

32 24 Maximizer CRM 10.5 SQL Conformance Minimum SQL Grammar Maximizer ODBC supports Minimum SQL Grammar as documented in Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide. The following table shows the Minimum SQL Grammar that Maximizer ODBC supports. Table 5 Minimum SQL Grammar Supported by Maximizer ODBC Minimum SQL Grammar Examples Comments DELETE INSERT SELECT UPDATE DELETE FROM notes WHERE Owner_Id = Kirsten Allen. INSERT INTO notes (Client_Id, Contact_Number, [Date], [Time], [Text]) VALUES ( 1234,0, 1995/ 03/20, 14:03:32:85, Appointment with CIO ). INSERT INTO RELATED_ENTRIES (RELATED_TO_ID, RELATED_TO_NUMBER, RELATED_FROM_ID, RELATED- FROM_NUMBER, DESC ) VALUES ( c, 0, c, 0, Insertion into related_entries table ). SELECT* FROM notes; SELECT Client_Id FROM notes WHERE Type=0. UPDATE notes SET [Text]= Appointment with CEO WHERE Client_Id= 1234 and Contact_Number=0 and Date= 1995/03/20 and Time= 14:03:32:85. Date, Time, and Text are reserved words and thus are enclosed in [. DESC is a reserved word. It is enclosed in double quotes. * should refrain from using Select* From... since all records will be returned.

33 Chapter 3 25 Core SQL Grammar Maximizer ODBC partially supports Core SQL Grammar as documented in Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide. The following table shows the Core SQL Grammar that Maximizer ODBC supports. Table 6 Core SQL Grammar Supported by Maximizer ODBC Core SLQ Grammar Examples Comments SELECT SELECT (continued) approximatenumeric-literal SELECT COUNT(Date), [Date] FROM notes GROUP BY [Date] HAVING [Date]> 1995/ 03/19. SELECT * FROM notes WHERE type = 0 INSERT INTO notes (type) VALUES (0) In addition to supporting a GROUP BY on a column-list, as specified in Microsoft s ODBC SDK Programmer s, the ODBC Driver has extended the syntax to support a GROUP BY on an expressionlist. HAVING is not supported without GROUP BY. For a more detailed description of the Maximizer ODBC Driver s extensions to the ODBC GROUP BY syntax, see the second list of this chapter. In addition to supporting an ORDER BY on a column-list, as specified in Microsoft s ODBC SDK Programmer s, the Maximizer ODBC Driver has extended the syntax to support an ORDER BY on an expression-list or on any expression in a GROUP BY expression-list. e.g., SELECT * FROM EMP ORDER BY a+b,c+d,e. This causes the result table to be ordered by three expressions: a+b, c+d, and e. If the expression is a single positive integer literal, then that literal will be interpreted as the number of the column in the result set and ordering will be done on that column. No ordering is allowed on Set Functions or on an expression that contains a Set Function. [UNION select-statement] is not supported. Sub-queries are not supported.

34 26 Maximizer CRM 10.5 Table 6 Core SQL Grammar Supported by Maximizer ODBC (Continued) Core SLQ Grammar Examples Comments betweenpredicate correlationname exact-numericliteral SELECT [Text] FROM notes WHERE type BETWEEN 0 AND 3 SELECT * FROM EMP notes WHERE notes.client_id = 1234 INSERT INTO notes (Contact_Number, Type) VALUES (49000,3) The syntax expression1 BETWEEN expression2 and expression3 returns TRUE if expression1>=expression2 or returns FALSE if expression1>= expression3. The Maximizer ODBC Driver supports both table and column correlation names. in-predicate set-function SELECT * FROM notes WHERE [Time] in 13:15:30:95, 14:03:32:8 5 ); SELECT COUNT (Type) FROM notes SELECT MIN([Time]) FROM notes MIN(expression), MAX(expression), SUM(expression), AVG(expression), COUNT(*), and COUNT(expression) are supported. COUNT(expression) counts all non-null values for an expression across a predicate. e.g. SELECT COUNT(A+B) FROM Q counts all the rows in Q where A+B does not equal NULL.

35 Chapter 3 27 Extended SQL Grammar Maximizer ODBC partially supports Extended SQL Grammar as identified in the following table. Table 7 Extended SQL Grammar Supported by ODBC Driver Extended SQL Grammar Examples Comments LEFT OUTER JOIN Two-table outer join: SELECT * FROM People LEFT OUTER JOIN notes ON People.Client_Id = Notes. Client_Id Three-table outer join: SELECT * FROM (People LEFT OUTER JOIN Notes ON People.Client_Id = Notes. Client_Id) LEFT OUTER JOIN Addr ON People.EmpID = Addr.EmpID. Embedded in vendor string: SELECT t1.client_id, ename FROM {oj People t2 LEFT OUTER JOIN notes t1 ON t2.client_id=t1.client_i d} Maximizer ODBC supports two-table outer joins as specified in Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide. In addition to simple two-table outer joins, Maximizer ODBC supports n-way nested outer joins. The outer join may or may not be embedded in a vendor string. If a vendor string is used, Maximizer ODBC will strip it off and parse the actual outer join text. Maximizer ODBC s implementation of LEFT OUTER JOIN goes beyond the syntax in Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide. For further information on the Driver s support of LEFT OUTER JOIN, see the Left Outer Join section in this appendix.

36 28 Maximizer CRM 10.5 Table 7 Extended SQL Grammar Supported by ODBC Driver (Continued) Extended SQL Grammar Examples Comments date-literal time-literal timestampliteral SELECT * FROM emp WHERE hire_date < ' ' SELECT * FROM emp WHERE hire_date < {d ' '} SELECT * FROM bday WHERE btime = '10:04:29' SELECT * FROM bday WHERE btime = {t '10:04:29'} SELECT * FROM bday WHERE btime = ' :25:00' SELECT * FROM bday WHERE btime = {ts ' :04:29'} Maximizer ODBC supports the following date literal format: YYYY-MM-DD Dates may be in the range of year 0 to Date constants may be expressed in SQL statements as a character string or embedded in a vendor string. Maximizer ODBC treats the character string representation as a string of type SQL_CHAR and the vendor string representation as a value of type SQL_DATE. This becomes important when conversions are attempted. For example, CONVERT({ d ' ' }, SQL_TIMESTAMP) is valid whereas CONVERT(' ', SQL_TIMESTAMP) returns an invalid SQL_TIMESTAMP value. Maximizer ODBC supports the following time literal format: HH:MM:SS Time constants may be expressed in SQL statements as a character string or embedded in a vendor string. Maximizer ODBC treats the character string representation as a string of type SQL_CHAR and the vendor string representation as a value of type SQL_TIME. Maximizer ODBC supports the following time literal format: YYYY-MM-DD HH:MM:SS Timestamp constants may be expressed in SQL statements as a character string or embedded in a vendor string. Maximizer ODBC treats the character string representation as a string of type SQL_CHAR and the vendor string representation as a value of type SQL_TIMESTAMP.

37 Chapter 3 29 Table 7 Extended SQL Grammar Supported by ODBC Driver (Continued) Extended SQL Grammar Examples Comments Date Arithmetic SELECT * FROM invoices WHERE invoice_date > ' ' AND invoice_date < {d ' '} + 30 SELECT * FROM payment WHERE payment_date - invoice_date > 30 Maximizer ODBC supports adding or subtracting an integer from a date where the integer is the number of days to add or subtract, and the date is embedded in a vendor string. (This is equivalent to executing a CONVERT on the date.) Maximizer ODBC also supports subtracting one date from another to yield a number of days. Note: The True Date option must be turned on. Delimited Identifiers in SQL Statements Column names and table names can occur as delimited identifiers if they contain non- ODBC standard characters. The delimiter character for delimiting the SQL syntax for these functions (see Appendix G of Microsoft s ODBC 2.0 Programmer s and SDK Guide) is a double quote (e.g. SELECT last-name FROM non-standard-tbl ).

38 30 Maximizer CRM 10.5 Scalar Functions String Functions Maximizer ODBC supports ODBC scalar functions that may be included in an SQL statement as a primary expression. The scalar functions that the Maximizer ODBC supports are described below. Example Numeric Functions SELECT [Date] FROM notes WHERE LCASE([Text]) = 'appointment with ceo' Example Date Functions SELECT * FROM notes WHERE MOD(Type,3) = 0 Example System Functions CONCAT LENGTH RTRIM LCASE LTRIM SUBSTRING LEFT RIGHT UCASE MOD CURDATE DAYOFMONTH MONTH CURTIME DAYOFWEEK YEAR SELECT * FROM emp WHERE YEAR(hire_date) < 1990 DATABASE IF NULL USER Example SELECT * FROM notes WHERE Owner_Id = USER() Note IF and NULL are internal to Maximizer ODBC.

39 Chapter 3 31 Conversion Functions CONVERT Example SELECT Client_Id FROM notes WHERE =CONVERT ([Date], SQL_DATE) + 30

40 32 Maximizer CRM 10.5 Data Types The following table shows all the ODBC SQL data types that Maximizer ODBC supports. Application writers can use SQLGetTypeInfo to determine which of these ODBC SQL data types are supported by Maximizer ODBC. (For further details on SQLGetTypeInfo, see Microsoft s ODBC 2.0 Programmer s and SDK Guide.) As the following table indicates, how Maximizer ODBC maps a data type to a default type, unless another data type conversion is specified by the user when SQLGetData or SQLBindCol is called, depends on whether or not the type to be mapped is part of a complex expression. (For a discussion of data type conversions, see Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide.) ODBC Data Type Mapping Table 8 ODBC Data Type Mapping ODBC Data Type Expression Default Type SUM/AVG SQL_BIT SQL_BIT N/A SQL_NUMERIC SQL_DOUBLE same SQL_DATE SQL_DATE N/A SQL_TIMESTAMP SQL_TIMESTAMP N/A SQL_DOUBLE SQL_DOUBLE same SQL_REAL SQL_DOUBLE same SQL_INTEGER SQL_DOUBLE same SQL_LONGVARBINARY N/A N/A SQL_LONGVARCHAR SQL_LONGVARCHAR N/A SQL_SMALLINT SQL_DOUBLE same SQL_CHAR SQL_CHAR N/A SQL_TIME SQL_TIME N/A SQL_TINYINT SQL_DOUBLE same SQL_VARCHAR SQL_VARCHAR N/A

41 Chapter 3 33 The table below describes each of the columns in the preceding table. Table 9 Description of Columns in ODBC Data Type Mapping Table Column ODBC Data Type Expression Default Type SUM/AVG Description The ODBC data type. If a column is part of a complex expression, Maximizer ODBC will convert the data type of that column to an expression default type in the result column. For example, in the query SELECT c1 * 10, where c1 is of type SQL_TINYINT, the result column will be of type SQL_DOUBLE. The type of the expression result column is determined at expression compile time and not at expression run time. All numeric expressions will be defaulted to the SQL_DOUBLE data type. This is the data type returned by the aggregate functions SUM and AVG. This column corresponds to the type of expression in the aggregate (e.g., SUM(expression)). An entry of same means that the type returned by SUM renders the same type as the expression. Limitations on SQL_LONGVARCHAR Maximizer ODBC imposes the following limitations on columns of data type SQL_LONGVARCHAR: LIKE predicate operates on the first 65,500 characters of the column data. All other predicates operate on the first 256 characters of the column data. SELECT statements with GROUP BY, DISTINCT, and ORDER BY return all the data but only order on the first 256 characters of the column data. In a single call to SQLGetData, the maximum number of characters returned by Maximizer ODBC for an SQL_LONGVARCHAR column is 65,500. Multiple calls must be made to SQLGetData to retrieve column data over 65,500 characters. Comparison of Floats Maximizer ODBC compares floating point numbers in comparison predicates using an almost equals algorithm. For example, = , and is >= The epsilon value is defined as DBL EPSILON in float.h ( e-016). This feature works for large numbers, but > and < will not be detected for small numbers; small numbers will be detected as equal.

42 34 Maximizer CRM 10.5 Representation of Float Infinity Maximizer ODBC has both a binary and a character representation of float infinity as shown in the following table. Table 10 Representation of Float Infinity Value Name Single BIN Positive Single Character Double BIN Positive Double Character Maximum Positive 0x7FEFFFFFFFFFFFFF Maximum Negative 0x7FEFFFFFFFFFFFFF Infinity Positive Infinity Negative 0x7F E999 0x7FF E999 0xFF E999 0xFFF E999 Maximizer Date and Time Maximizer ODBC presents the Maximizer Date and Time in character string format (i.e., Date_string and Time_string ). The application, however, can convert the Date_string in SQL_CHAR to SQL_DATE if so desired in any date operations. The same is true for Time_string. CAUTION Time_string is in HH:MM:SS:HS format (i.e., Maximizer supports the hundredth of a second, such that a loss in precision may result in converting time in SQL_CHAR to that in SQL_TIME).

43 Chapter 3 35 Other Characteristics SQL Statement Limitations Stack Size Precision and Scale Collate Sequence Maximizer ODBC applies the following restrictions to SQL statements: Maximum of 1000 characters in a literal Maximum of 300 ANDed predicates (e.g., SELECT * FROM emp WHERE c1 AND c2 AND c3 use two ANDed predicates). Depending on the stack size allocated by the calling application, limitations on very long expressions (e.g., SELECT * FROM emp where c1 = ) may also apply. (See Stack Size below.) Maximum of 256 columns in a CREATE TABLE statement Maximum of 64 characters in a table or column and in index names A character in a character string literal may be any ANSI character between 1 and 255 decimals. A single quote (') must be represented as two consecutive single quotes (''). Maximizer ODBC requires a minimum available stack size of 10K from the calling application, and in some cases may require more. Therefore, we recommend an available stack size of at least 20K. Maximizer ODBC cannot determine the precision and scale of data values of type SQL_NUMERIC. Maximizer ODBC assumes that all tables accessed during an active connection have the same collate sequence. All tables within a query statement must have the same collating sequence for comparison operations to work properly.

44 36 Maximizer CRM 10.5 Closing an Open Table Concurrency Calling SQLFreeStmt with the SQL_CLOSE option changes the SQLState but does not close the open tables used by the hstmt. To close the tables currently used by hstmt, SQLFreeStmt must be called with the SQL_DROP option. In the following example, the Emp and Dept tables remain open: SQLPrepare(hStmt, SELECT * FROM Emp, Dept, SQL_NTS); SQLExecute(hStmt); SQLFetch until NO_DATA_FOUND SQLFreeStmt(hStmt, SQL_CLOSE); When SQLPrepare is subsequently called on by the hstmt, the tables used in the previous statement are closed. For example, when the following call is made, both the Emp and Dept tables will be closed by Maximizer ODBC: SQLPrepare(hStmt, SELECT * FROM Customer,SQL_NTS); The following call would then close the table Customer: SQLFreeStmt(hStmt, SQL_DROP); The timeliness of data, dynamic or snapshot, is determined by whether or not execution of a query results in a sort. Queries with DISTINCT, GROUP BY, or ORDER BY will result in a sort by Maximizer ODBC, unless an index exists that satisfies the required ordering. For those queries that do not result in a sort by Maximizer ODBC, the data fetched will be from the data files (called dynamic). For those queries that do result in a sort by Maximizer ODBC, the data fetched will be from a temporary table (called a snapshot). The temporary table is built from the required data in the original data file at SQLExecute time. Temporary tables greater than 64K will be written to a temporary file in the directory indicated by the application user s TEMP environment variable. If there is not enough disk space on the user s system to write the temporary file, the sort will fail. If the user is short of disk space on a local machine, the TEMP environment should be set to a network drive. Note For some sort operations (e.g., for SELECT statements where long data columns are included in the select-list or for SELECT statements with GROUP BY), Maximizer ODBC may use bookmarks that the Driver assumes are persistent within a SELECT statement. A situation may arise in which another application updates or deletes the row that a bookmark references. To avoid this situation, an application may set an exclusive lock on the table being sorted through a call to SQLSetStmtOption, with foption = 1153 and vparam = 1.

45 Chapter 3 37 Extensions to the ODBC GROUP BY Syntax GROUP BY Syntax In addition to the GROUP BY syntax in a SELECT statement as specified in Microsoft s ODBC 2.0 Programmer s and SDK Guide, the Maximizer ODBC Driver supports an extended GROUP BY syntax as follows: [GROUP BY expression,[expression]...] If an SQL_LONGVARCHAR expression is used in a GROUP BY clause, the Maximizer ODBC Driver only uses the first 256 characters of that expression. GROUP BY Semantics A GROUP BY query returns a result set which contains one row of the select-list for every group encountered. (See Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide for the syntax of a select-list.) For example, SELECT Dept FROM Emp GROUP BY Dept uses the Emp Table to produce a list of unique departments. Another example might be to count the number of employees in each department: SELECT Dept, COUNT(*) FROM Emp GROUP BY Dept In this case, the result set contains a list of unique departments and the count of employees in each department. SELECT Statement select-list As the above examples show, a select-list in a SELECT statement containing a GROUP BY clause can contain: An exact replica of one of the expressions in the GROUP BY expression-list. The exact replica can actually be a sub-expression in the select-list. For example, SELECT Dept, Salary + Commission, Salary + Commission / AVG(Salary+Commission) * 100 FROM Emp GROUP BY Dept, Salary + Commission is valid since no expression using ambiguous values occurs. Α set function. The rows operated on by the set function are those rows remaining after the WHERE search condition is applied. For example, in SELECT COUNT(*) FROM Emp WHERE Salary > GROUP BY Dept COUNT(*) counts only those rows in the Dept groups that have Salary >

46 38 Maximizer CRM 10.5 HAVING With GROUP BY The expressions in a HAVING clause may contain constants, set functions, or an exact replica of one of the expressions in the GROUP BY expression-list. For example, SELECT Dept, COUNT(*) FROM Emp GROUP BY Dept HAVING COUNT(*) > 2 returns departments where the count of employees is greater than 2. SELECT Dept, COUNT(*) FROM Emp GROUP BY Dept HAVING COUNT(*) > 2 AND Dept BETWEEN '120' AND '180' returns departments between 120 and 180 where the number of employees is greater than 2. Note The Maximizer ODBC Driver does not support HAVING without GROUP BY. The Maximizer ODBC Driver has implemented LEFT OUTER JOIN using SQL92 (SQL2) as a model. Since SQL2 is a new SQL standard and adequate descriptions do not exist, this appendix provides an explanation of this new outer join syntax and its associated meaning in the Maximizer ODBC Driver.

47 Chapter 3 39 Left Outer Join Syntax Vendor Strings The syntax taken here is a subset of the entire SQL92 syntax, which includes right outer joins, full outer joins, and inner joins. The TableRefList non terminal below occurs after the FROM keyword in a SELECT statement and before any subsequent WHERE, HAVING, and other clauses. Note the cooperatively recursive nature of TableRef and LeftOuterJoin. In other words, a TableRef can be a left outer join that can include TableRef s which, in turn, can be left outer joins ad infinitum. TableRefList : TableRef [, TableRefList] TableRef OuterJoinVS [, TableRefList] TableRef : TableName [CorrelationName] LeftOuterJoin ( LeftOuterJoin ) LeftOuterJoin : TableRef LEFT OUTER JOIN TableRef ON SearchCond The SearchCond contains join conditions which in their usual form are LT.ColumnName = RT.ColumnName, where LT is left table, RT is right table, and ColumnName represents some column within a given domain. No literals can exist in the ON SearchCond. The syntax above includes but goes beyond the current ODBC syntax in Appendix C of Microsoft's ODBC 2.0 Programmer s and SDK Guide. Furthermore, the vendor string escape sequence at the beginning and end of the LeftOuterJoin does not change the core syntax of the outer join. As shown in the above syntax, the Maximizer ODBC Driver accepts outer join syntax without the vendor strings. However, for applications that want to comply with ODBC across multiple databases, the vendor string construction should be used. Since ODBC vendor string outer joins do not support more than two tables, it may be necessary to use the syntax shown below in Example 4 below rather than that shown in Examples 2 and 3.

48 40 Maximizer CRM 10.5 Examples of Left Outer Join The following four tables provide examples of Left Outer Join. Employee FirstName LastName DeptID EmpID Frankie Avalon D103 E1 Gordon Lightfoot D102 E2 Lawrence Welk D101 E3 Bruce Cockburn D102 E4 Department DeptID LocID Name D101 L1 TV D102 L2 Folk Address EmpID E1 E2 Street 101 MemLane 14 Yonge St. Location LocID L1 L2 Name PlanetX PlanetY

49 Chapter 3 41 Example 1: Simple Two-way Left Outer Join SELECT * FROM Emp LEFT OUTER JOIN Dept ON Emp.DeptID = Dept.DeptID This simple two-way outer join produces the following result set: Emp Dept FirstName LastName DeptID EmpID DeptID LocID Name Frankie Avalon D103 E1 NULL NULL NULL Gordon Lightfoot D102 E2 D102 L2 Folk Lawrence Welk D101 E3 D101 L1 TV Bruce Cockburn D102 E4 D101 L1 TV Notice the NULL entry for Frankie Avalon. This occurs because no DeptID of D103 was found in the Dept table. In a standard (INNER) join, Franky Avalon would have been dropped from the result set altogether. Algorithm The algorithm that the Maximizer ODBC Driver uses in the above example is as follows: Taking the left table (TL), traverse the right table(tr), and for every case where the ON condition is TRUE, return a result set row composed of the appropriate TR row appended to the current TL row. If the ON condition is false, in all cases of TR row create a row instance of TR with all column values NULL. That result set, combined with the current TL row, becomes the returned result set row. In the simple two-way left outer join shown above, Emp is TL and Dept is TR. Note Although irrelevant to the algorithm, appending TL to TR assumes proper projection as specified in the select list of the query. This projection ranges from all columns (i.e., SELECT * FROM...) to only on column in the result set (i.e., SELECT FirstName FROM...).