ASNA DataGate for SQL Server 8.2

Release Notes for ASNA DataGate for SQL Server 8.2.162.3

Released to GA on March 5, 2010

Software Requirements

ASNA DataGate for SQL Server versions 8.2.137.0 and above are compatible with Windows Vista and Windows Server 2008.
ASNA DataGate for SQL Server supports Microsoft SQL Server 2000, 2005, and 2008.

Installation Notes

ASNA DataGate for SQL Server Stored Procedures must be installed in every instance of Microsoft SQL Server for which DataGate access is desired. You will have the chance to install the Stored Procedures during the installation of DataGate for SQL Server. Depending on your SQL Server configuration, the stored procedures dialog may not be able to automatically detect your SQL instance name. If this is the case, you may manually enter the instance name in the following format:

NETBIOS-NAME\INSTANCE-NAME

Where NETBIOS-NAME is the name of the machine hosting the SQL Server and INSTANCE-NAME is the name of the SQL instance. You may also install the Stored Procedures to the default SQL instance by entering the following:

(local)

SQL Server Express 2005 requires the following minimal configuration:

TCP networking must be enabled via Surface configuration.
UDP port 1434 must be enabled in any firewall that may be running.
TCP port 1433 must be enabled in any firewall that may be running.
SQL Server Browser service must be enabled and started. It is installed disabled by Microsoft.

Connecting to SQL Server on Microsoft's XP Pro Service Pack 2

Installing Microsoft's XP Pro Service Pack 2, by default, enables the built-in Windows firewall settings which interfere with SQL Server connectivity. These settings, unless changed, won't let you connect to SQL Server with either SQL Server's own Enterprise Manager or with ASNA's DataGate for SQL Server (DSS).

The Windows Firewall closes ports such as 445 that are used for file and printer sharing to prevent Internet computers from connecting to file and print shares on your computer or to other resources. When SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP ports and these ports must be open. SQL Server clients that are trying to connect to SQL Server will be not be able to connect until SQL Server is set as an exception in Windows Firewall. To set SQL Server as an exception in Windows Firewall, use the steps that are listed here.

Please see http://devnet.asna.com/documentation/readme/dss_82_readme.htm for other installation details.

Licensing Changes

DataGate for SQL Server 8.2 employs a new License Manager that eliminates the duplicate user counts that were encountered in DataGate for SQL Server 5.0

Issues Resolved since the previous GA Release (8.2.154.0)

Asna Services

Case 12039. AVR IDE 9.0 permanent license registration should also register licenses for DG/Windows 8x, DSS 8x and WebPak 8x.
Case 11899. Fix auto registrations following AVR 8.2 installation.
Case 11743. Construct IpcServerChannel to allow the network sid.
Case 11707. Complete automatic license upgrade from Monarch 4.0 to 4.1.
Case 11705. Refactor duplicate isXYZPermLicense methods to use a common isPermLicense method.
Case 11500. Forward all registration methods to new method.
Case 8696. Register DG Windows and 8.x Compilers when installing 9x WebPak trial.
Case 8696. New license model for counting cores for WebPak 9.1
Case 9203. Debug configuration was masking a string formatting, parameter list bug causing the Release version to throw a memory access execption.
SvcHost platform changed back to x86 necessary for Windows 64-bit compatibility.
Case 8930: DataGate WebPak 9x trial license code does not generate a license.

DataGate Server

Case 11922. Must use VT_EMPTY if bstr is zero length for SQL 2000.
Case 11919. Implement a useful format ID generator for print files in dg400.
Case 11827. Handle tables and views with a domain-qualified schema/owner name.
Case 11664. Fix walk of REG_MULTI_SZ and include instances from 32-bit node if running 64-bit system.
Case 11799. Fix bug where the peer protocol level could be changed to an invalid value, causing trouble for RPCs dependent on later functionality.
Case 11671. Grant *PUBLIC/*USE authority to license objects created via pcode::externalize().
Case 11664. Get list of SQL Server instances from registry rather than udp messaging.
Case 5500. Expose file text from "pal" filedef object, so that dg400 can use it in the CRTPF, CRTLF, and CRTPRTF commands. In dg400 "set object text" rpc, escape single-quote chars in the string so the method does not fail.
Case 10922. Fix query for ASNA stored procedure installation/configuration to work with a case sensitive 'master' database.
Case 10485. Handle dgRuntimeException thrown from dgChannel::getBytes, and return "invalid file" error to client.
Fix low-probability uninitialized variable bug found by new VS C++ runtime in the 9.0.30729.1 SP.
Case 10248. Return dgEmDNOTFND ('Library Not Found') if target library doesn't exist for duplicate object.
Include DBPART_STATUS flag for DBBINDING entries requiring status information.
Use correct rowsize when creating accessor.

Registration Assistant

Case 12011. Rename 8.x and 9.x WebPak nodes.

Issues Resolved in version 8.2.154.0

DataGate Server

Case 9299. Restore side-effect behavior of ReadSequential "No Current Record" after ReadRange returns "Not Found"
Case 9273. Monitor for CPF0600 series exceptions in RNMOBJ command
Case 9129. Use escape sequence for single-quotes in text fields.
Case 8799. Handle special *FILE key descriptions during open.
Case 8209. Parse schema name from file name when enumerating directory and getting filedef info.

Issues Resolved in DataGate for SQL Server 8.2.150.1

Case 7774	Realign negative sign bit when mapping zone-to-zoned.
Case 7908	Set current database before getting table statistics so the ActiveRecords property works properly against DSS.
Case 6946	AVR 4.x app using DGCpyFile causes Datagate copyData rpc no longer fails. The error produced was: Runtime error '1119 - the 'To' file could not be created'.
Case 7113	WRITE on disk file records using Boolean fields when the target database is Microsoft SQL Server no longer hangs the application.
Case 7150	Clarified an installation error message when framework 2.0 is missing.
Case 7426	DataGate Exception (SQL OLE DB error) no longer occurs on READ of SQL table/view after the file's RecCount property is used.
Case 7445	Add UPDLOCK hint to compensate for cursor scroll lock behavior change introduced in SQL Server 2005. In SQL Server 2005, cursor scroll locks acquire a lock upgrade from S (Shared) to U (Update), unless a higher lock hint is specified in the query. SQL Server 2000 transparently adds a U lock hint for scroll lock cursors. The SQL Server 2005 behavior allows for better concurrency but opens up the chance of deadlocks for concurrent cursors. Use the UPDLOCK hint to achieve the behavior you want. For more information, see Table Hint on Transact-SQL. Adding the UPLOCK hint along with the existing ROWLOCK hint causes SQL 2005/2008 to behave as SQL 2000 with respect to record locking.
Case 7500	Collating sequence upgraded to handle different languages.

DataGate for SQL Server 8.2 - (Series Items)

Access denied. You do not have permission to perform this action or access this resource.