Microsoft SQL Server Release Notes
Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.
See TIBCO Scribe® Online Connector For Microsoft SQL Server for more information.
Version 1.3.0
Released April 10, 2018.
New And Noteworthy
There are no new features in this release.
Closed Issues
62163
When running a app where Microsoft SQL Server is the source, records returned from SQL by the Query are sorted by the Net Change date and the Most Recent Record Processed date is set to the date of the last record used in a target operation. (Case # 63518)
62432
Added support for the ApplicationIntent=ReadWrite connection property in the Additional Parameters field on the Connection dialog. (Case # 63641)
62575
If you change the case on a field name or table column in your source data after replicating data to Microsoft SQL Server, subsequent replications ignore the case change and continue to replicate data to the correct table and column in Microsoft SQL Server. (Case # 63848, 64147)
Known Issues
SCMSSQL-42
Summary: When using Microsoft SQL Server as a target datastore for a Replication Solution, if the source data contains a Date datatype, that type is converted to a DateTime datatype. If the date value in the source data is earlier than 1/1/1753, such as 0001-01-01, the solution stops with a fatal error similar to the following: (Case # 01936053)
Workaround: Manually modify the datatype to Date in the target Microsoft SQL Server database. Then, use an Integration Solution to create the records in the SQL database. Using a Replication Solution after modifying the datatype will not solve the issue because Replication Solutions reset the datatype each time they execute.
SCMSSQL-38
Summary: When using Windows authentication with batch processing enabled, data is inserted into the target table one record at a time instead of in batches. (Case #01925766)
Workaround:Contact Support for hotfix SCMSSQL-34.
SCMSSQL-33
Summary: When running a Replication Solution that replicates a very large entity, such as an Audit table, the Net Change process may time out when determining which records are new or updated. Errors similar to the following are generated: (Case # 01910410)
Error Message: Object Reference not set to instance of an object.
Message: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Workaround: Work with your database administrator to create an index on the table you are attempting to replicate.in the Microsoft SQL server database.
SCMSSQL-32
Summary: If you send NULL parameters to SQL Server Stored procedures, the connector sends blank or zero length strings. (Case # 01894158)
Workaround: To produce a DB null in a formula, use the word NULL without enclosing it in quotes. Contact Support for Hotfix SCMSSQL-27.
SCMSSQL-26
Summary: If you create a table in your Microsoft SQL Server server database that contains a period in the name, TIBCO Cloud™ Integration - Connect interprets the information before the period as the schema. For example, a table named DB.TEST is treated as schema name DB, table name TEST. This generates errors similar to the following: Entity ‘DB.TEST’ was not found. The metadata for this connection may have changed. (Case # 01884653)
Workaround: Rename the table and exclude periods from the name.
SCMSSQL-19
Summary: If your Microsoft SQL Server database has multiple schemas and one or more schemas have tables with periods (.) in the name, TIBCO Cloud™ Integration - Connect may interpret the tables as duplicates. For example, [dbo].[DEL.CRM.US_PRODUCT] and [dbo].[DEL.CRM_US_PRODUCT] are interpreted as the same table name. This generates errors similar to the following when attempting to retrieve metadata: (Case # 01856579)
An item with the same key cannot be added
Workaround: Rename the schema or table, or try the following:
- Abstract the tables via a SQL view.
- Create a user that has access only to those views.
- Setup a Microsoft SQL Server connection in TIBCO Cloud™ Integration - Connect using that user.
SCMSSQL-15
Summary: If the size of a source field is larger than the size of the target field in your Microsoft SQL Server database, a truncation error similar to the following is generated, but the field name is not included: (Case # 01827348)
String or binary data would be truncated.
Workaround: Refer to the following Knowledge Base article: Replication Services Error: Failed to insert record
SCMSSQL-14
Summary: The Connector cannot add new columns to a Data replication app target database if the Microsoft SQL Server database access is set to Windows authentication with the fully qualified domain format “Username@domain.com”. (Case # 01795528)
Workaround: Use Windows authentication with the FQDN format domain\Username or SQL authentication.
SCMSSQL-11
Summary: The version of Microsoft .Net Framework used with this Connector does not support querying decimal values with a large number of values to the right of the decimal point, such as 20 places to the right of the decimal, and generates Conversion Overflow errors. (Case # 01794013)
Workaround: Use a Native Query and the CAST () function to convert the field to a lower decimal type or convert it to char ().
SCMSSQL-9
Summary: Fields that are type rowversion cannot be used as filters and generate errors similar to the following: (Case # 01784190)
ERROR: Exception Type : InvalidExecuteQueryException
Message : The following error has occurred in the SQL Connector: Implicit conversion from data
type varchar to timestamp is not allowed.
Workaround: Contact Support for Hotfix SCMSSQL-4.
SCMSSQL-3
Summary: If Agent Debug logging is enabled, stored procedures executed by the Connector return the following error: (Case # 01768187, 01793507, 01728424)
“The given key was not present in the dictionary.”
Workaround: Do not enable debug on the Agent.
Version 1.2.0
Released November 30, 2017.
New And Noteworthy
- Added support for Batch Processing for the following operations:
- Create (45679)
- Delete (46763)
- Added support for SQL tables with names that start with numbers. (45682)
- Validated support for Microsoft SQL Server 2017: Enterprise, Standard, and Express. (48409)
Closed Issues
15512
When a Data replication app is running, if the target table is missing a required primary key constraint, the table is recreated before the associated records are replicated. (Case # 79680, 79688)
32222 / 48928
When the server time on the source datastore and the server time on the agent server differed, some records were not Updated or Deleted during the execution of a Data replication app. (Case # 75482, 75489)
36974 / 38071
Using the Create Block with Microsoft SQL Server sometimes returns more than one success message per record, which was generating an Error Number: 0 error. (Case # 52419, 53406)
43462
When using Windows Authentication via a group to access Microsoft SQL Server, the default schema could not be accessed preventing the Connector from retrieving metadata. (Case # 57408)
44134 / 46610
Improved retry logic when the Connector receives an inbound message to be processed by a Request/Reply flow to solve intermittent exceptions similar to the following: (Case # 57390)
The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection.
44479
Using the Query Block to access a Microsoft SQL Server database was locking third-party systems out of that database until the agent was stopped. (Case # 56080, 58688)
48970 / 49125
Data replication apps were attempting to alter the decimal precision on float data types resulting in reduced performance for large datasets. (Case # 60150)
52181
When using Microsoft SQL Server as a target datastore for Data replication apps, the most recent date in the SCRIBE_MODIFIEDON target field for each table was used as a filter to query the corresponding source entity for new, changed, and deleted.This resulted in some deleted records being reprocessed in cases where the date in the SCRIBE_DELETEDON target field was newer than the most recent date in the SCRIBE_MODIFIEDON target field.
52387
The TargetTimeout setting on the Connection configuration dialog used the default value of 30 seconds regardless of the actual setting. (Case # 61295)
Fall 2015 Release
New And Noteworthy
The Microsoft SQL Server Connector was installed automatically with any agent installation. In this release, the Microsoft SQL Server Connector has been moved to the TIBCO Cloud™ Integration - Connect Marketplace. (1802, 1809)
This Connector has been enhanced to support the Connect cloud agent regardless of the location of the Microsoft SQL Server database including Microsoft Azure. The database can be on premise or in the cloud. (3383)
Closed Issues
There are no closed issues in this release.
August 2015 Release
New And Noteworthy
Added support for TargetTimeout and QueryTimeout parameters in the Additional Parameters field on the Connection dialog for the TIBCO Cloud™ Integration - Connect Connector for Microsoft SQL Server. Use these parameters to modify the default timeout settings for target and source operations when processing Microsoft SQL Server records.(D10007 / # Case 68829)
Closed Issues
There are no new features in this release.
May 2015 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
9658
A Timeout Expired error was generated when trying to delete a large number of records in Execution History. (Case # 68967)
Winter 2015 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
Improved SQL Azure Support in Data replication apps to generate a Fatal Error and stop running if there are any record errors. TIBCO Cloud™ Integration - Connect sometimes failed with timeout errors that resulted in missing records in the target database. Data replication updated the last modified time based on newer records that were processed correctly, and the missing records were not replicated in a future run.
9093
Apps that contained maps where the source was Microsoft SQL Server and the maps were created using older metadata sometimes generated an invalid field name nativequery.bounddate error when you attempted to save them. (Case # 62024)
9338
Data replication apps using Microsoft SQL Server as the target were not replicating some entities. (Case # 64949)
October 2014 Release
New And Noteworthy
- Enhanced the SQL connection dialog to include Additional Parameters and Object Filter fields. Additional Parameters is an optional field used to specify one or more connection parameters that enable or disable the use of Stored Procedures, Tables, or Views. Additional connection parameters defined on the MSDN reference site can also be used. Object Filter is used to select or limit the stored procedures, tables and/or views returned in metadata when you connect to your SQL database.
- Added support for complex data types, such as geometry, geography, and user-defined types.
- Validated support for Microsoft SQL Server 2014: Enterprise, Standard and Express.
Closed Issues
8187
After a bulk process was performed on an entity and the changes were confirmed, subsequent runs of the app caused those entities to be reprocessed, even if no changes were made to those entities between the two runs. (Case # 54406)
9098
Replicating to a SQL database when the SQL connection was configured for Windows Authentication and the source datastore had schema changes caused errors. In addition, if tables were manually deleted from the target database, they were not recreated during subsequent replication jobs. (Case # 62960, 62986)
July 2014 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
8944
The Microsoft SQL Server connector was fixed to release connections that it is no longer using. This should end most execution failures caused by all connections in the connection pool being in use. (Case # 61753)
August 2013 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
7136
Errors were generated when adding additional fields to Lead Entity (Case # 49613, 50206, 51866)
7753
Data replication app SQL Azure - A transport-level error occurred when receiving results from the server (Case # 53101)
June 2013 Release
New And Noteworthy
New Native Query Block – When using a native Microsoft SQL Server connection as your source in an Integration app flow, the Native Query Block allows you to write your own query, rather than using the structure provided by the regular Query block. For more information, see Native Query Block.
Support for Stored Procedures with Microsoft SQL Server (Beta) — For Microsoft SQL Server connections, an Execute block (similar to a Create block) is available to allow you to execute simple stored procedures within Integration app flows.
Closed Issues
There are no closed issues in this release.
April 2013 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
6990
Replicating CRM 2011 to SQL Azure resulted in a fatal error that it was losing connection to SQL Azure. The error was: (Case#49941)
“Fatal Exception: System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred”
July 2012 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
6374
Unable to see Entities using Oracle ODBC Connection – This issue manifested itself across SQL, ODBC, and OLEDB connectors in cases where two entities were reported with the same name but different cases, and a third entity, even, may exist with the same name and a numeric suffix (e.g., account, Account, Account2). This has been fixed such that we will be able to list these entities in the field lists without stack errors. (Case # 47001)
May 2012 Release
New And Noteworthy
TIBCO Cloud™ Integration - Connect now officially supports Microsoft SQL Server 2012 (Enterprise, Standard , and Express editions)
Closed Issues
There are no new features in this release.
March 2012 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
6070 / 6080 / 6083
Text and Microsoft SQL Server Connectors now support entity and field names with spaces and special characters — For Text and Microsoft SQL Server Connectors, you can now map field and entity names that contain spaces and most special characters, with some caveats:
- Field or entity names that contain special characters will display in TIBCO Cloud™ Integration - Connect as follows:
- Any space or special character is dropped from the name.
- If the resulting name duplicates another existing entity name, each duplicate will be numbered (for example, field1, field2… For 10 or more duplicates, the fields will be numbered field01, field02… and so on).
- To use these fields or entities in maps (including in formulas), use the adjusted names as they appear in TIBCO Cloud™ Integration - Connect. The original names will still display in the flow page Property pane and in any runtime errors that reference these objects.
- Periods (.) and double quotes (“) are currently not supported in entities and field names. This is a known issue that is under investigation.
February 2012 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
May 2011 Release
New And Noteworthy
TIBCO Cloud™ Integration - Connect now supports a wider number of Microsoft SQL Server versions including Microsoft SQL Server Express and SQL Azure. For information about all supported software
Closed Issues
There are no closed issues in this release.
April 2011 Release
New And Noteworthy
Users can now connect to the Microsoft SQL Server replication database via Windows Authentication or SQL Authentication. Earlier versions of TIBCO Cloud™ Integration - Connect only supported SQL Authentication.
TIBCO Cloud™ Integration - Connect now supports custom Microsoft SQL Server data types. Columns that are defined with custom data types in a Microsoft SQL Server table will no longer appear as fields with a datatype of "Unsupported". Instead, these fields now display as having a data type of "Object." You can now link to or from fields with custom data types, although you may need to convert the data using a data conversion function such as TOSTRING.
Closed Issues
Updated agents received an error that an index array was out of bounds when attempting to establish a connection to Microsoft SQL Azure. Newly installed agents worked correctly. Microsoft recently released updated versions of their code libraries which are used by the agent. However, the latest versions of those code libraries were not installed as part of the agent update process. With this new agent release, all agents will have the latest Microsoft libraries and are able to connect to Microsoft SQL Azure. (Case #40130).
January 2011 Release
New And Noteworthy
If you build a flow in TIBCO Cloud™ Integration - Connect and select Microsoft SQL Serveras your source connection, you can now select database views as source entities (in addition to tables). Note that database views will display in the list of target entities, but cannot be selected.
Closed Issues
There are no Closed Issues in this release.