|
|
|
Preserve Imported Data Files upon SQL DROP
FairCom DB SQL brings many advanced SQL capabilities to application data that was not originally created in SQL. Legacy application tables can be linked, or imported, to SQL. FairCom DB SQL now defaults to always removing linked physical data and index files when performing a DROP from SQL as expected from SQL standards. However, there are frequently cases where removal of the data file is not appropriate nor expected. Rather, it is best to only remove the SQL system table linkage entry. A new configuration option is available to preserve the physical files.
SQL_OPTION DROP_TABLE_DICTIONARY_ONLY
Identify "Bad" Records from Legacy Data Linked to SQL
Multiple customers in production, in particular those using SQL callbacks, have encountered a situation where there was an error interpreting field content.
FairCom RTG offers a SQL syntax extension, ctoption(badrec), which helps identify "bad" records and fields that cannot be properly interpreted. We extend this function into the general SQL engine itself to aid identifying "bad" records for all applications.
Example:
SELECT * FROM <table> ctoption(badrec)
When using the ctoption(badrec) syntax, only failing records are returned and error information is logged in sqlserver.log.
