Skip to content
Thoroughbred Software InternationalThoroughbred Software InternationalThoroughbred DocumentationDocs

Troubleshooting

The following provides troubleshooting information specific to SQL Server.

Section titled “Link Error”

Error 0 occurs opening the Link and no locks seem to be active in Basic or from an SQL application.

Since the Link header is read internally by Basic when opening the Link, this record needs to be accessible at open time. If it is extracted through Dictionary-IV, for example, the error 0 occurs. Setting the PRM READONLY parameter in the IPLINPUT file will clear this situation.

Server Table Error

Section titled “Server Table Error”

Errors opening server tables.

  • Verify that the DEV line for the server where the table resides is present in the appropriate IPLINPUT file.
  • Verify the user has SQL Server credentials for the Database and Table.
  • Verify the Link has a Table name. If the associated Format has text fields defined, verify that the Link also has a Text File Name.

Unexpected Sorting Sequence or Errors Accessing SQL Tables

Section titled “Unexpected Sorting Sequence or Errors Accessing SQL Tables”
  • If a Link header has been configured to access a server table defined on the server as a view, unexpected results ranging from incorrectly sorted data to tsmssql process failures may result. It is suggested that access to the server be limited to objects defined as tables. SQL does not support certain operations on views such as SELECT …FOR UPDATE.
  • Be sure that the primary key index is present.
  • Check the collation sequence for the SQL Server Database. The default collation sequence may not be ASCII.

Hanging on a WRITE

Section titled “Hanging on a WRITE”

Under certain circumstances a WRITE may hang if the row is locked in SQL Server using a share (S) or share row exclusive (SRX) type lock. This occurs because the INSERT/UPDATE part of the SQL code for a WRITE statement does not support NOWAIT and will wait until the lock is removed by the SQL Server process. The share and share row exclusive type locks are not generated by any Basic code, and therefore this situation cannot occur between Basic tasks.

Some Access Using Sorts is Very Slow

Section titled “Some Access Using Sorts is Very Slow”

Sorts that contain references to substrings of fields may not perform as well as sorts on full fields. This is because SQL Server has no facility to define indexes on portions of fields. For more information see the Performance Tuning section of this manual.

From the TS DataServer for MS SQL Server, version 8.9.1. Open this page in the PDF