提供7*24专业Sybase数据库远程及现场技术支持,Sybase ASE及Sybase SQL Anywhere数据库修复服务,
请联系电话: (微信),QQ: 289965371!
We supply technical support for Sybase ASE and Sybase SQL Anywhere, also have many years of experience in recovering data from damanged Sybase devices.
Please contact us:
Phone:
Wechat: 13811580958
QQ: 289965371 联系我们获取数据库技术支持!
Email: 289965371@qq.com
扫描下方微信,联系我们:
扫描雨翰数据恢复官方微信获取专业数据库恢复服务

 

随着Sybase被完全整合到SAP下,Sybase原来的支持网站被SAP Support Portal取代。
只有购买了SAP服务的用户才能使用账号登录SAP Support Portal进行介质下载、补丁升级、报Incident等。
考虑到Sybase数据库的初学者或者没有购买原厂服务的Sybase客户情况,现提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息。
在SAP Support Portal网站或者google上搜索Targeted CR List for ASE,可以看到针对不同版本的CR(CR表示Change Request)简单描述信息列表。
需要注意的是:Targeted CR List for ASE列出的CR虽然绝大多数是BUG,但有一些是更改需求。
以下提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息!

如有问题,请联系我!

QQ :289965371 联系我们获取数据库技术支持!
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:638835
CR Number:   638835
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 4111 24 Aug 2010 Fixed
Description
Calls to the system function property('platform') would have returned 'WindowsVista'

when the server was running on Windows 7, Windows 2008, or Windows 2008 R2. This has been fixed.



CR:638848
CR Number:   638848
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2572 24 Aug 2010 Fixed
11.0.1 2484 24 Aug 2010 Fixed
10.0.1 4111 24 Aug 2010 Fixed
9.0.2 3982 24 Aug 2010 Fixed
12.0.1 3012 27 Sep 2010 Fixed
Description
A few improvements have been made to ADOX/OLEDB table creation.



Long types are now mapped to SQL Anywhere long types. For example, an adLongVarChar column is now mapped to "LONG VARCHAR" instead of "CHAR(0)".



Wide types are now mapped to SQL Anywhere nchar types instead of char types. For example, adWChar is now mapped to "NCHAR" and adLongVarWChar is now mapped to "LONG NVARCHAR".



An adSingle column with no specifed precision will now default to REAL rather than FLOAT(0), which generated a syntax error.



An adDecimal column with no specified precision and scale will now default to DECIMAL rather than DECIMAL(0,0), which generated a syntax error.



An adNumeric column with no specified precision and scale will now default to NUMERIC rather than NUMERIC(0,0), which generated a syntax error.



An adLongVarBinary column will map to the IMAGE type rather than BINARY(0), which generated a syntax error.



An adCurrency column is now supported and will map to a column of type MONEY.



An adDate column is now supported and will map to a column of type DATETIME.



If a table or column name is not defined, OLEDB will no longer fault with a NULL pointer reference. Instead, the name "undefined" will be used.



The following code fragment is a VBScript example for creating a table using ADOX statements.



Set db = CreateObject( "ADOX.Catalog" )

Set ntable = CreateObject( "ADOX.Table" )

ntable.Name = "testTable"

ntable.Columns.Append "Col_1", adNumeric

ntable.Columns.Append "Col_2", adDate

ntable.Columns.Append "Col_3", adChar, 32

ntable.Columns.Append "Col_4", adVarChar, 32767

ntable.Columns.Append "Col_5", adLongVarChar

ntable.Columns.Append "Col_6", adLongVarWChar

db.Tables.Append ntable



CR:638849
CR Number:   638849
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2573 23 Aug 2010 Fixed
11.0.1 2484 23 Aug 2010 Fixed
12.0.1 3015 27 Sep 2010 Fixed
Description
Statements which CREATE, DROP or ALTER synchronization profiles were not being recorded in the transaction log. If a database server needed to recover the effects of one of these statements, recovery could have failed. This has been fixed.



CR:638854
CR Number:   638854
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3015 24 Aug 2010 Fixed
Description
The Server Licencing utility (dblic) has a limit on the length of the user name and company name that it stores in the license file. When it truncated the name, it could have done so in the middle of a multi-byte character resulting in a mangled name. This has been fixed.



CR:638856
CR Number:   638856
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2484 24 Aug 2010 Fixed
Description
The Interactive SQL utility, the Console utility, and Sybase Central, could have terminated without an error message. This could have happened when closing an "Options" dialog, and possibly at other points, due to an uninitialized variable. This has been fixed.



CR:638859
CR Number:   638859
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 2573 24 Aug 2010 Fixed
Description
When connection parameters were specified on the MobiLink Monitor command line, the splashscreen did not close. This has been fixed.



CR:638862
CR Number:   638862
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2573 24 Aug 2010 Fixed
11.0.1 2484 24 Aug 2010 Fixed
12.0.1 3015 27 Sep 2010 Fixed
Description
The Interactive SQL utility would have crashed if a file was imported and then subsequently text was pasted into the editor. This has been fixed.



CR:638896
CR Number:   638896
Product Name:   MobiLink
Product Component:   MobiLink Agent
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2573 24 Aug 2010 Fixed
12.0.1 3015 27 Sep 2010 Fixed
Description
The MobiLink Agent for central adminstration of remote databases could have displayed unlocalized messages in its output window when running at v4 or higher verbosity. This has been fixed.



CR:638897
CR Number:   638897
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 24 Aug 2010 Fixed
12.0.1 3017 27 Sep 2010 Fixed
Description
The result set display format (Scrolling Table versus Text) was ignored when disconnecting from one type of database (e.g. SQL Anywhere), and then connecting to another (e.g. UltraLite). This has been fixed.



CR:638899
CR Number:   638899
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3015 24 Aug 2010 Fixed
Description
The Options window had a set of radio buttons ("Show only the first result set" and "Show all result sets") which determined which result sets were displayed for statements that return more than one result set. UltraLite statements can return at most a one result set, so this option has ignore, and has now been removed.



CR:638900
CR Number:   638900
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 25 Aug 2010 Fixed
11.0.1 2485 25 Aug 2010 Fixed
10.0.1 4111 25 Aug 2010 Fixed
12.0.1 3016 27 Sep 2010 Fixed
Description
If a certain statement was prepared and described that returned no result set, and then a DDL statement caused the same statement to return a result set, client statement caching could have caused the statement to be redescribed incorrectly. This was a client statement caching peformance optimization, and before this change, there was no way to disable this incorrect behavior. For example, the following statements executed in dbisql would have returned an error on the second call foo() statement:

create or replace function foo() returns int begin return 1; end;

call foo();

create or replace procedure foo() begin select 2; end;

call foo();



This has been fixed so that if client statement caching is disabled by setting the max_client_statement_cached option to 0 for the connection, such a statement is now described correctly.



CR:638903
CR Number:   638903
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2573 25 Aug 2010 Fixed
12.0.1 3015 27 Sep 2010 Fixed
Description
A race condition in the server could have caused it to crash on shutdown. This problem only affected Solaris (Intel and SPARC), HP, AIX and Mac OS X. This has now been fixed.



CR:638982
CR Number:   638982
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3016 24 Aug 2010 Fixed
Description
Creating an external procedure with a CREATE PROCEDURE statement that contained both a RESULT and LANGUAGE clause, but that did not contain a DYNAMIC RESULT SETS clause, would have incorrectly defaulted the number of dynamic result sets to 0 instead of 1. This problem has now been fixed and the dynamic result sets (if not specified) will now default to 0 if no result clause exists, and will otherwise default to 1 if a RESULT clause does exist. Note that as before, the DYNAMIC RESULT SETS value is only meaningful if a LANGUAGE clause is specified.



CR:638986
CR Number:   638986
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2573 24 Aug 2010 Fixed
11.0.1 2485 24 Aug 2010 Fixed
10.0.1 411 24 Aug 2010 Fixed
12.0.1 3016 27 Sep 2010 Fixed
Description
The Query Editor could have crashed if the last time it was opened a join had been added to the query, but the join type was left unspecified (blank). This has been fixed.



CR:639002
CR Number:   639002
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2573 24 Aug 2010 Fixed
11.0.1 2485 24 Aug 2010 Fixed
12.0.1 3016 27 Sep 2010 Fixed
Description
Changes made to the WHERE and HAVING tabs in the Query Editor were ignored after the Options button was clicked. This has been fixed.



CR:639012
CR Number:   639012
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 25 Aug 2010 Fixed
11.0.1 2490 09 Sep 2010 Fixed
12.0.1 3031 27 Sep 2010 Fixed
Description
The script events publication_nonblocking_download_ack, nonblocking_download_ack and generate_next_last_download_timestamp may have incorrectly been passed the client Remote ID. This would have occurred for non-SQL scripts as well as SQL scripts that used the question mark notation. This has been fixed so that the Remote ID is no longer passed to these scripts.



Note that the documentation is correct.



CR:639016
CR Number:   639016
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 30 Aug 2010 Fixed
11.0.1 2485 30 Aug 2010 Fixed
10.0.1 4111 30 Aug 2010 Fixed
12.0.1 2574 27 Sep 2010 Fixed
Description
Attempting to execute queries that used the FOR XML clause, may have caused the server to crash when failures were encountered while fetching data. This has been fixed.



CR:639018
CR Number:   639018
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2573 25 Aug 2010 Fixed
11.0.1 2485 25 Aug 2010 Fixed
10.0.1 4111 25 Aug 2010 Fixed
12.0.1 3016 27 Sep 2010 Fixed
Description
The Query Editor could have crashed when opened if the initial SELECT statement contained "*" and at least one explicit column name in the column list. This has been fixed.



CR:639021
CR Number:   639021
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2576 30 Aug 2010 Fixed
12.0.1 3022 27 Sep 2010 Fixed
Description
The server may have become unresponsive when an error occurred that should have been ignored. This has been fixed. The following console message was sometimes, but not always observed on Windows 7: "TCP Listener shutting down (64)".



This change also includes the following enhancements:

- When a listener terminates, it now always writes a console message identifying the protocol and the network address, ie. HTTPS, {::}:443

- An IgnoreCodes protocol option has been added to HTTP and HTTPS protocols



CR:639028
CR Number:   639028
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2573 25 Aug 2010 Fixed
12.0.1 3016 27 Sep 2010 Fixed
Description
Conversion of some time strings to a timestamp would have failed.

A time specified as hours followed by the AM/PM designator could not have been converted to a timestamp. For example:

select cast( '11am' as time );



The work-around is to include minutes:

select cast( '11:00am' as time );



A time that included microseconds, but did not include seconds could not have been converted to a timestamp. For example:

select cast('00:00:.930' as time)



The work-around is to include seconds:

select cast('00:00:00.930' as time)



These problems have been fixed.



CR:639107
CR Number:   639107
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 4162 17 Dec 2010 Fixed
Description
In a mirroring system it was possible for the mirror server to get the error: "*** ERROR *** Assertion failed: 100904 (10.0.1.4075) Failed to redo a database operation (page number and offset) - Error: Table in use". This could also have occurred when dropping a global temporary table, or during database recovery, without using a high availability environment. This has been fixed.



CR:639139
CR Number:   639139
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3016 25 Aug 2010 Fixed
Description
In SQL Anywhere 12 the new read-only scale-out feature was introduced which allows creation of an arrangement of read-only copy nodes to offload reporting or other operations that require read-only access to the database. Now, customers can obtain at-a-glance information about the health and availability of their scale-out configuration by using the SQL Anywhere Monitor. When monitoring a SQL Anywhere resource, a new widget option is available, "SQL Anywhere Scale-Out Topology". When monitoring the root node in the scale-out system, the new Topology Widget provides an overview of the parent/child relationships of Nodes in the scale-out system, as well as basic health and availability information.







The information displayed in the Topology Widget is as follows:



Server Name - The name of the node given when creating the scale-out system. See "CREATE MIRROR SERVER statement" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/create-mirror-server-statement.html*d5e37248



Type - The node type defined when creating the scale-out system. See "CREATE MIRROR SERVER statement" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/create-mirror-server-statement.html*d5e37248



State - The connection status of the node. Can be one of "connected" or "disconnected". See "sa_mirror_server_status system procedure" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/sa-mirror-server-status-sysproc.html*d5e70531



Connections - The current number of connections to this node. See "sa_mirror_server_status system procedure" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/sa-mirror-server-status-sysproc.html*d5e70531



Last Updated - The time the server information was last updated. See "sa_mirror_server_status system procedure" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/sa-mirror-server-status-sysproc.html*d5e70531. Note that this value is not necessarily the same as the last time the Monitor fetched topology information for this scale-out system.



CR:639140
CR Number:   639140
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 26 Aug 2010 Fixed
11.0.1 2486 26 Aug 2010 Fixed
12.0.1 3022 27 Sep 2010 Fixed
Description
When the Options window was opened from the Query Editor, all of the options for the Text Completer would have been inadvertently turned off. This has been fixed.



CR:639159
CR Number:   639159
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 26 Aug 2010 Fixed
11.0.1 2486 26 Aug 2010 Fixed
10.0.1 4113 26 Aug 2010 Fixed
12.0.1 3017 28 Sep 2010 Fixed
Description
In some cases, calling the system procedure sa_get_request_times() may have caused the server to crash. This has now been fixed.



CR:639238
CR Number:   639238
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2486 26 Aug 2010 Fixed
10.0.1 4113 26 Aug 2010 Fixed
Description
In very rare cases, doing full validation on a table may have caused the server to crash. For this to have occurred, the following conditions had to hold:

1) Validation was being done online.

2) The table contained blobs.

3) Table blobs were being heavily modified by other concurrent requests.

4) The right timing happened between the validation process and the blob update

process.



This has been fixed.



CR:639289
CR Number:   639289
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3038 30 Aug 2010 Fixed
12.0.0 2583 30 Aug 2010 Fixed
12.0.1 2996 28 Sep 2010 Fixed
Description
The Relay Server extension for the Apache webserver now supports Apache 2.2.15 on Linux. Apache 2.2.15 now offers more security enhancements.



CR:639298
CR Number:   639298
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3018 17 Jan 2011 Fixed
12.0.0 2574 17 Jan 2011 Fixed
11.0.1 2486 17 Jan 2011 Fixed
Description
Creating a server message store would have fail when attempting to create a new, encrypted SQL Anywhere database for the store. This has been fixed.



CR:639373
CR Number:   639373
Product Name:   SQL Anywhere Monitor
Product Component:   Monitor Migrator
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2575 30 Aug 2010 Fixed
12.0.1 3019 28 Sep 2010 Fixed
Description
When migrating a SQL Anywhere Monitor from 11.0.1 to 12.0.0 it was possible that alert thresholds for the new 12.0.0 alerts could have been incorrect for the migrated resources. This has been fixed. When the new alert thresholds were added, their columns in the database were given default values. Unfortunately, during the reload process DEFAULTS ON was not being specified. Defaults have now been turned on.



CR:639397
CR Number:   639397
Product Name:   MobiLink
Product Component:   MobiLink Agent
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2575 30 Aug 2010 Fixed
12.0.1 3019 28 Sep 2010 Fixed
Description
The MobiLink Agent for central adminstration of remote databases may not have shut down, or may not have shut down in a timely manner, when retrying a task that had a large number of retries or a large retry delay. This has been fixed.



CR:639535
CR Number:   639535
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2578 07 Sep 2010 Fixed
11.0.1 2490 07 Sep 2010 Fixed
12.0.1 3026 28 Sep 2010 Fixed
Description
Queries that did a sequential table scan could have failed to return all the rows in the table. This would usually only have happened when doing a DELETE over a non-transactional temporary table. This could also have happened to regular base tables with concurrent deleters as well, but the chances of this would have been very low in practice.



A workaround is to issue deletes over a non-transactional temporary table multiple times.



CR:639646
CR Number:   639646
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3019 31 Aug 2010 Fixed
Description
A new alert has been added to the SQL Anywhere Monitor to provide users with notification if their scale-out system has a large percentage of disconnected nodes. The new "Scale-out Nodes Disconnected" alert takes a user-supplied threshold value. If during data collection it is detected that this threshold of disconnected nodes is exceeded, an alert is raised. The alert also contains a list of all the servers currently disconnected.



CR:639651
CR Number:   639651
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 2986 31 Aug 2010 Fixed
Description
The typing completion feature has been improved.



1. The text completer now opens automatically when typing. This can be turned off from the Options window by clearing the "Open automatically" box on the "Text Completion" page.

2. SQL statements and keywords are now included in the list of suggestions.

3. The completer now correctly handles databases where strings are treated as case-sensitive but identifiers are not.

4. Performance has been improved.

5. The keyboard accelerators for use when the completion list is open have changed:



Old Accelerator New Accelerator Function

Tab Ctrl+A Show a context-free list of matches

+ Ctrl+Plus Add the item with its parameter list

* Ctrl+Asterisk Add the item with its parameter and type list

" Ctrl+Apostrophe Add the item enclosed in quotation marks



6. In addition to the Enter key, pressing the Tab key while the completer list is open accepts the selected item and closes the completer.

7. Columns from internal text tables are no longer shown.

8. Completed database object names, which are also SQL keywords, are automatically quoted.

9. If a function key is pressed, or if the menu bar is used while the completer is open, the selected completion item is added, the completer is closed, and then the function key (if any) is processed.

10. The "Text Compeleter" tab in the Options window has been clarified. Options to control whether tables, views, stored procedures, and SQL functions have been removed; the SQL parsing in good enough to guide the selection of the suggested items.



CR:639656
CR Number:   639656
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2576 31 Aug 2010 Fixed
11.0.1 2487 31 Aug 2010 Fixed
10.0.1 4115 31 Aug 2010 Fixed
12.0.1 3022 28 Sep 2010 Fixed
Description
In some cases the Start Server in Background utility (dbspawn) could have returned the generic error, -80 (Cannot start server), instead of returning the real error. In other cases, the server could have crashed on shutdown. This has been fixed.



CR:639657
CR Number:   639657
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2577 02 Sep 2010 Fixed
12.0.1 3024 28 Sep 2010 Fixed
Description
The server may have picked an unoptimal best plan for queries requiring a reversed index scan if they bypassed the SA Optimizer (i.e., the bypass was used for optimizing the query). This has been fixed.



For example:

create index idx on T(X);

select max(T.X) from T;



CR:639704
CR Number:   639704
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2576 01 Sep 2010 Fixed
12.0.1 3020 28 Sep 2010 Fixed
Description
When performing arithmetic on DOUBLE values, if one of the inputs was NULL, an arithmetic overflow error could have been spuriously reported instead of computing the NULL value properly. The problem only affected 32-bit platforms, and has now been fixed.



CR:639706
CR Number:   639706
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2576 01 Sep 2010 Fixed
11.0.1 2488 01 Sep 2010 Fixed
12.0.1 3023 28 Sep 2010 Fixed
Description
The startup error messages "Failed to become a daemon" and "'%1' is not a valid engine name" were not localized on UNIX systems. This has been corrected.



CR:639712
CR Number:   639712
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2578 01 Sep 2010 Fixed
11.0.1 2490 01 Sep 2010 Fixed
10.0.1 4117 01 Sep 2010 Fixed
12.0.1 3023 28 Sep 2010 Fixed
Description
The OLE DB provider's TABLES, TABLES_INFO, and VIEWS schema rowset support procedures do not identify MATERIALIZED VIEWs and TEXT CONFIGURATION objects correctly. Materialized views are now reported as "VIEWS", and text configuration objects are now identified as "TEXT", in the TABLE_TYPE column.



Also, the OLE DB provider's TABLES schema rowset included an unnecessary and undocumented column "PREFIXSYSOWNED". This column has been removed from the rowset to match similar behavior of the stored procedure than produces theTABLES_INFO schema rowset.



The OLE DB provider's TABLE_CONSTRAINTS schema rowset support procedure fails with the error "Column 'check' not found". This has been fixed.



The Upgrade utility (dbupgrad) should be used to update the OLE DB schema rowset support in any database used with ADO, ADOX or OLE DB.



CR:639814
CR Number:   639814
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2577 03 Sep 2010 Fixed
12.0.1 3025 28 Sep 2010 Fixed
Description
In rare circumstances, performing spatial operations could have caused the server to crash, corrupt server memory, and possibly corrupt database file contents. The problem was more likely to occur when spatial operations were active at a time when both cache pressure was high and operations such as checkpoints or cache shrinking occurred. This problem has been fixed.



CR:639825
CR Number:   639825
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Windows 2000
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 10 Sep 2010 Fixed
11.0.1 2493 10 Sep 2010 Fixed
10.0.1 4120 10 Sep 2010 Fixed
12.0.1 3032 28 Sep 2010 Fixed
Description
The 32-bit authentication value sent to MobiLink clients was being truncated to 16-bits. This has been fixed. In order to use this fix, both clients and server must be updated. If the use of this fix is not required, it is not necessary to upgrade both the clients and server.



CR:639836
CR Number:   639836
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2577 01 Sep 2010 Fixed
11.0.1 2489 01 Sep 2010 Fixed
12.0.1 3024 28 Sep 2010 Fixed
Description
A SQL Anywhere "root" web service did not resolve a URL when the database name was provided without a terminating slash, i.e. http://localhost/dbname. The server would have returned a 404 "Not Found" HTTP status. The following URL forms were also rejected with a 404 "Not Found":

http://localhost/dbname?arg

http://localhost/dbname/?arg



The problem existed for both secure and insecure services, and has now been fixed.



CR:640008
CR Number:   640008
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3009 02 Sep 2010 Fixed
Description
The following enhancements have been made to the typing completer:



- The owner name is no longer added to completed table, view, or procedure names if there is only one object in the system catalog with the given name.



- A new option has been added: "The Enter key completes text". When the option is checked, pressing the Enter key completes the text with the selected item. When the option is not checked, pressing Enter will insert a newline into the text editor, but will not complete any text. This option is checked by default. If multi-line SQL statements are usually typed, it may be that leaving this option unchecked will result in fewer inadvertent completions being done.



Note: If the arrow keys are used to change the selection in the completer list, or one of the list items is selected, pressing Enter will complete the text with the selected item. In all cases, pressing the Tab key will close the completer and complete the text in the editor.



- The completer can now complete method names for spatial columns. e.g. if the insertion point immediately follows "ST_" in any of the following statements, the completer will show only methods for the spatial column "Shape":



select S.Shape.ST_ from SpatialShapes S

select Shape.ST_ from SpatialShapes S

delete from SpatialShapes where Shape.ST_

delete from SpatialShapes S where S.Shape.ST_

update set Description='x' from SpatialShapes S where S.Shape.ST_



(Note: This is not a complete list of supported syntaxes)



When trying to complete a method name for an object other than a table/view column, the completer will suggest method names as well as other database objects whose names match the method name prefix. For example, if the insertion point is at the end of the following statement:



select (new Point()).ST_



the completer will list spatial methods, but also st_geometry_dump, StartDate, Status, etc.



CR:640015
CR Number:   640015
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3002 02 Sep 2010 Fixed
Description
The MobiLink server on Windows and Linux systems now supports consolidated databases running on an ASE 15.5 server. In order to properly support it, an ASE native ODBC driver from Sybase SDK 15.5 ESD#2 or later is required.



CR:640027
CR Number:   640027
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2577 03 Sep 2010 Fixed
12.0.1 3025 28 Sep 2010 Fixed
Description
Recovery of ALTER DBSPACE or DROP DBSPACE could have failed if the original statement was executed when there were inactive pooled connections. This has been fixed.



CR:640035
CR Number:   640035
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2484 03 Sep 2010 Fixed
12.0.1 2988 28 Sep 2010 Fixed
Description
The entry in the documentation for the ml_add_column system procedure incorrectly suggested a behaviour change, that "ml_add_column names are overidden by names from the client, if they are supplied." The ml_column entries always override names and orderings sent up from the client.



Note that the point is moot for the vast majority of deployments, because most deployments: (a) have one true column ordering, and (b) do downloads. MobiLink currently does not support downloads to remotes with different column orderings with the same names using the same script version. Use different script versions, each with a known column ordering, to support downloads to different column orderings.



CR:640037
CR Number:   640037
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3025 03 Sep 2010 Fixed
Description
The Create Group wizard now allows the members (Agents) for a group to be selected by pointing to a text file which contains the names of the Agents. The ability to add members by browsing the Agents defined in a consolidated database is also still supported.



Note, the text file containing the Agent names must have each Agent name on its own line.



CR:640081
CR Number:   640081
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2577 03 Sep 2010 Fixed
12.0.1 3025 28 Sep 2010 Fixed
Description
When specifying a non-default date, time, or timestamp_format option, the date/time values could have been truncated in the XML file produced by the UltraLite Unload Database utility (ulunload). This has been fixed.



CR:640109
CR Number:   640109
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2490 14 Sep 2010 Fixed
Description
The deployment wizard was failing when attempting to register one of our v4.0 .Net assemblies on systems where version 4.0 of the .NET framework was not installed. This has been fixed.



CR:640110
CR Number:   640110
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2582 14 Sep 2010 Fixed
11.0.1 2494 14 Sep 2010 Fixed
10.0.1 4121 14 Sep 2010 Fixed
12.0.1 3036 28 Sep 2010 Fixed
Description
When executing a remote procedure call to an ASE server, if the procedure involved output parameters, then there was a chance the call would have failed with the remote error "output parameters will only be returned from this stored procedure when you use only parameter markers to pass parameter values". This problem has now been fixed and the remote call should now execute correctly.



CR:640194
CR Number:   640194
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 2580 09 Sep 2010 Fixed
Description
For queries containing predicates of the following forms:

A = B

A <> B

A [NOT] IN ( ... )

A = ANY ( ... )

A <> ANY ( ... )

A = ALL ( ... )

A <> ALL ( ... )



where A was a geometry column with a spatial index, extra rows may have been returned if the optimizer chose a plan that accessed the index with a scan predicate. This has been fixed.



CR:640205
CR Number:   640205
Product Name:   MobiLink
Product Component:   iAS Branded ODBC Drivers
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2583 03 Sep 2010 Fixed
11.0.1 2495 03 Sep 2010 Fixed
10.0.1 4122 03 Sep 2010 Fixed
12.0.1 3038 16 Sep 2010 Fixed
Description
In some cases, the iAS ODBC driver for Oracle could aborted the operation and given the following Oracle error:

ORA-03145: I/O streaming direction error



This would have occurred when the driver was used to send NULL BLOBs to a table in an Oracle database and then the rows were fetched back from this table using the same database connection, and the Oracle database was running with a multi-byte character set. This has now been fixed.



CR:640222
CR Number:   640222
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3026 03 Sep 2010 Fixed
Description
Remote schema names can now be imported into a project from a consolidated database. Import remote schema names can be done a number of ways:



1. Right-click "Remote Schema Names" in the "Folders" panel and click the new "Import" menu item.



2. When adding a consolidated database to a project, either with the Project wizard or the Consolidated Database wizard, the wizards will automatically check if there are any remote schema names defined in the consolidated database that are not already in the project. If there are, the wizards will ask if they should be imported.



CR:640232
CR Number:   640232
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2578 07 Sep 2010 Fixed
11.0.1 2490 07 Sep 2010 Fixed
12.0.1 3026 28 Sep 2010 Fixed
Description
Dropping a temporary procedure could have caused recovery to fail if the procedure name was qualified with an owner. This has been fixed.



CR:640239
CR Number:   640239
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2578 07 Sep 2010 Fixed
11.0.1 2490 07 Sep 2010 Fixed
12.0.1 3026 28 Sep 2010 Fixed
Description
The SetupVSPackage.exe utility did not update SQL Server Integration Services mapping files and the ProviderDescriptors.xml file for 64 bit DTS on 64 bit Windows. This problem has been fixed.



CR:640240
CR Number:   640240
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2572 07 Sep 2010 Fixed
11.0.1 2490 07 Sep 2010 Fixed
10.0.1 4117 07 Sep 2010 Fixed
12.0.1 3012 28 Sep 2010 Fixed
Description
Execution of an ATTACH TRACING statement with a LIMIT clause, either by size or by time, would generally have failed to limit the size of the trace captured. This has been fixed.



CR:640241
CR Number:   640241
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2578 07 Sep 2010 Fixed
11.0.1 2490 07 Sep 2010 Fixed
12.0.1 3026 28 Sep 2010 Fixed
Description
In rare circumstances, the QAnywhere C++ client could have deleted a received and acknowledged message before the acknowledged status was transmitted back to the sender. This has been fixed.



CR:640243
CR Number:   640243
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2578 07 Sep 2010 Fixed
Description
When adding a widget in the SQL Anywhere Monitor, the drop-down listing all the resources would have displayed the resources in random order. This has been fixed so that the resources are now displayed in alphabetical order.



Note that this problem does not apply to new Alert List and Resource List widgets.



CR:640410
CR Number:   640410
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2579 07 Sep 2010 Fixed
12.0.1 3030 28 Sep 2010 Fixed
Description
Attempting to drop a user declared within a web service may have caused the server to crash if the service was recently accessed with an HTTP request. This has been fixed.



The following illustrates the issue:



create user web identified by web;

create procedure web.sp_test()

begin

select 1;

end;

create service test type 'HTML' user web authorization off secure off url off as call sp_test();



A "DROP user web" command crashes the server if one or more database connections for the user "web" happen to be pooled.



CR:640411
CR Number:   640411
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 4119 07 Sep 2010 Fixed
Description
Statistics about the Disk Transfer Time (DTT) of additional dbspaces were not loaded at database startup, so they were not available for the optimizer to generate better plans. This has been fixed.



CR:640423
CR Number:   640423
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 09 Sep 2010 Fixed
12.0.1 3031 28 Sep 2010 Fixed
Description
Queries containing predicates that composed ST_SRID(int) or ST_Transform(int) with a spatial predicate, could have caused a crash. This only happened for queries that bypassed the optimizer (single table queries).



For example, the following query could have caused a crash:

SELECT *

FROM tablename

WHERE geometry_column.ST_Transform( 0 ).ST_Intersects( new ST_Point( 0, 0, 0 ) ) = 1



This has been fixed.



CR:640434
CR Number:   640434
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2579 07 Sep 2010 Fixed
11.0.1 2492 07 Sep 2010 Fixed
12.0.1 3030 28 Sep 2010 Fixed
Description
A failed attempting to connect to a server which required the server to be autostarted could have leave the server running. This could have occurred if the server started had the server stop permission set to a value other than None, and server failed to start the database for certain reasons.



For example, if asatest.db is an Adaptive Server Anywhere 9 database, the following would start a server that was left running:

dbping -d -c "uid=dba;pwd=sql;dbf=asademo.db;start=dbsrv11 -x none"



This has now been fixed.



CR:640440
CR Number:   640440
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 14 Jan 2011 Fixed
Description
The "Check for Updates" window did not close when the Esc key was pressed unless the "Cancel" button was visible. This has been corrected so that pressing the key now always closes the window.



CR:640461
CR Number:   640461
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2579 08 Sep 2010 Fixed
11.0.1 2492 08 Sep 2010 Fixed
12.0.1 3030 28 Sep 2010 Fixed
Description
In certain very rare circumstances it was possible that the SQL Anywhere Monitor could have shut down data collection incorrectly. This would have occurred in environments where the SQL Anywhere Monitor server was consistently under heavy load. This issue has been fixed.



CR:640470
CR Number:   640470
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3030 14 Sep 2010 Fixed
Description
On systems running the Chinese version of Windows XP, some private use characters were displayed incorrectly in the following places:

1. The result set table's long value window

2. The query tree (left hand pane) of the Plan Viewer



This has been corrected.



CR:640486
CR Number:   640486
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3030 09 Sep 2010 Fixed
Description
The Agent wizard and property sheets now allow a description to be set for agents that are defined. The description is free form text.



CR:640515
CR Number:   640515
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2492 09 Sep 2010 Fixed
Description
An application could have failed to reconnect to a database created with a user specified EncryptionControl. UltraLiteJ was failing to call EncryptionControl.initialize() on connect, hence the database could not be opened. This has been fixed.



To workaround the problem, use code that explicitly invokes the initialize() method prior to connecting to the database. For example:

// password = password to access database

// config = config object to access database

// MyEncryptionControl = user defined class extending EncryptionControl

EncryptionControl enc = new MyEncryptionControl();

enc.initialize( password );

config.setPassword( password );

config.setEncryption( enc );

conn = DatabaseManager.connect( config );



CR:640525
CR Number:   640525
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3043 20 Sep 2010 Fixed
12.0.0 2585 20 Sep 2010 Fixed
Description
The readability of the query returned by the REWRITE function has been improved.



CR:640540
CR Number:   640540
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3043 20 Sep 2010 Fixed
12.0.0 2585 20 Sep 2010 Fixed
11.0.1 2497 20 Sep 2010 Fixed
Description
The property QueryOpened was not being increased if a reusable cursor was opened. This has been fixed.



CR:640543
CR Number:   640543
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2582 14 Sep 2010 Fixed
11.0.1 2495 14 Sep 2010 Fixed
12.0.1 3037 28 Sep 2010 Fixed
Description
The result set returned for a query with GROUP BY and ORDER BY clauses was not correctly ordered if both clauses contained the same integer constant. This has been fixed.



CR:640578
CR Number:   640578
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
3061 07 Oct 2010 Fixed
12.0.0 2594 07 Oct 2010 Fixed
Description
The UltraLiteJ utilities, Database Information utility (ULjInfo), Database Load utility (ULjLoad) , Database Unload utility (ULjUnload) , and Database Transfer utility (ULjDbT), would have failed when attempting to run on 64-bit Windows They were failing because they referenced a JRE that was not installed. This has now been corrected.



CR:640579
CR Number:   640579
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3062 12 Oct 2010 Fixed
12.0.0 2595 12 Oct 2010 Fixed
11.0.1 2507 12 Oct 2010 Fixed
Description
Attempts to unload an UltraLiteJ database using the ULjUnload utility would have resulted in a Null Pointer exception if the database had publication IDs that were not numbered continuously from 1. This can occur if publications are created then dropped. For example:

CREATE PUBLICATION pub1 ...

CREATE PUBLICATION pub2 ...

DROP PUBLICATION pub1



This has been fixed.



CR:640582
CR Number:   640582
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 09 Sep 2010 Fixed
12.0.1 3032 28 Sep 2010 Fixed
Description
UltraLite does not support user-defined database properties. So when executing the statement SELECT db_property(bad-property), a SQLE_UNKNOWN_PROPERTY error was generated when attempting to move to the first row of that result set. Applications written in C/C++, Javascript, ObjectiveC and .Net would have generated that error, however the Interactive SQL utility would not have displayed that error, but would have returned no rows and displayed no heading to the result set (appearing to be hung). This is now fixed.



CR:640589
CR Number:   640589
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 09 Sep 2010 Fixed
11.0.1 2492 09 Sep 2010 Fixed
12.0.1 3031 28 Sep 2010 Fixed
Description
The utility SetupVSPackage.exe did not modify the file machine.config for the 64 bit .NET Framework. The machine.config file is now updated for both the 32 bit and 64 bit Frameworks on 64 bit Windows.



CR:640596
CR Number:   640596
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 09 Sep 2010 Fixed
11.0.0 2492 09 Sep 2010 Fixed
12.0.1 3031 28 Sep 2010 Fixed
Description
The iAnywhere Solutions 12 Oracle ODBC driver would not have been installed by the deployment wizard. The driver was not being registered, and thus did not appear in the ODBC administrator. This has now been corrected.



CR:640597
CR Number:   640597
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 09 Sep 2010 Fixed
12.0.1 3031 28 Sep 2010 Fixed
Description
Starting with Version 12.0.0, on Windows computers, numbers are now formatted with the thousands separator that is shown in the Windows Control Panel. They were always being shown though on Windows Vista and Windows 7, even if they had been turned off on the Control Panel. This has now been corrected. This problem had already been fixed for Windows XP and earlier (see Engineering case 631033).



This fix also affects the "Data" tab for tables and views in Sybase Central.



CR:640610
CR Number:   640610
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 09 Sep 2010 Fixed
12.0.1 3031 28 Sep 2010 Fixed
Description
When using the deployment wizard to create an MSI install, the Relay Server plugin did not appear in the list of plugins, and thus was not installed. The rsplugin files have now been added.



CR:640611
CR Number:   640611
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 09 Sep 2010 Fixed
12.0.1 3031 28 Sep 2010 Fixed
Description
The Visual Studio Server Explorer, the Data Source Configuration Wizard, and the Entity Data Model Wizard, did not list materialized views. This has been fixed.



CR:640621
CR Number:   640621
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2579 09 Sep 2010 Fixed
11.0.1 2490 09 Sep 2010 Fixed
10.0.1 4117 09 Sep 2010 Fixed
12.0.1 3030 28 Sep 2010 Fixed
Description
Depending on timing, stopping a server with the Stop Server utility (dbstop) and immediately restarting it with the Start Server in Background utility (dbspawn) could have return the error:

DBSPAWN ERROR: -85

Communication error



The communication error could also have occurred if the server was started without dbspawn. This has been fixed.



CR:640776
CR Number:   640776
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2495 01 Oct 2010 Fixed
Description
When running an MSI install that was generated by the Deployment wizard, the ulodbc11.dll was not self registered. This has now been fixed.



CR:640779
CR Number:   640779
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3032 10 Sep 2010 Fixed
Description
In Sybase Central, the "Commands" panel for remote tasks now contains a help button for the command being edited.



CR:640780
CR Number:   640780
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 09 Sep 2010 Fixed
12.0.1 3032 28 Sep 2010 Fixed
Description
The SQL Server Import and Export wizard did not list materialized views. This has been fixed by changing the values returned in the 'TABLE_TYPE' column of the schema set returned by the call to SAConnection.GetSchema("Tables") for materialized views to 'VIEW'.



CR:640786
CR Number:   640786
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 10 Sep 2010 Fixed
11.0.1 2493 10 Sep 2010 Fixed
10.0.1 4120 10 Sep 2010 Fixed
12.0.1 3032 28 Sep 2010 Fixed
Description
Calls to the GetSchema method would have return an error when the restrictions vector size was less than the total number of restrictions. For example, if 2 restrictions were specified for a schema rowset that took up to 3 restrictions, the GetSchema call would have resulted in an error indicating that 3 restrictions were expected. The error was due to the fact that the array size is 2, not 3. This problem has been fixed.



CR:640804
CR Number:   640804
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3032 10 Sep 2010 Fixed
Description
With the introduction of read-only scale-out systems in SQL Anywhere 12, it was possible that a scale-out system without mirroring could have lead the SQL Anywhere Monitor to incorrectly raise alerts about the arbiter and/or mirror server being unavailable when no such problem existed. This has been fixed.



CR:640821
CR Number:   640821
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3100 15 Nov 2010 Fixed
12.0.0 2611 15 Nov 2010 Fixed
11.0.1 2524 15 Nov 2010 Fixed
10.0.1 4148 15 Nov 2010 Fixed
Description
It was possible to get the following validation errors:

Page x of database file "<database file name>" references a table (y) that doesn't exist

or

Orphaned page (x) found in database file "<database file name>".



The database server could have left some pages in a state where they cannot be reused. The database would have continued to function normally in this state but it is possible to regain the lost pages by rebuilding the database file. This most likely would have occurred in a non-system dbspace, and has now been fixed.



CR:640832
CR Number:   640832
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2580 10 Sep 2010 Fixed
12.0.1 3032 28 Sep 2010 Fixed
Description
After following the scale out tutorial described in the documentation, the overview panel in Sybase Central would have shown warnings for the mirror and arbiter. This has been fixed. The mirror and arbiter are now excluded from the overview panel details when only scale out is used.



CR:640901
CR Number:   640901
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2582 14 Sep 2010 Fixed
11.0.1 2495 14 Sep 2010 Fixed
10.0.1 4122 14 Sep 2010 Fixed
12.0.1 3037 28 Sep 2010 Fixed
Description
Revoking table column permissions may have failed with the SQL error 'Permission denied: you do not have permission to revoke permissions on "Column1"' if there were column permissions granted from multiple grantors. This has been fixed.



CR:640923
CR Number:   640923
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2582 13 Sep 2010 Fixed
11.0.1 2494 13 Sep 2010 Fixed
12.0.1 3036 28 Sep 2010 Fixed
Description
Simple queries using the aggregate GROUPING(1), but with no GROUP BY clause, would have returned the meaningless error "Invalid expression near GROUPING(1)". This has been fixed. The server now returns the error "Argument to GROUPING aggregate must be a grouping column in the GROUP BY clause".



CR:640952
CR Number:   640952
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3720 01 May 2012 Fixed
11.0.1 2799 01 May 2012 Fixed
Description
On Solaris systems, the server would have failed to start if the filesystem for the temporary file ($SATMP) was of a size greater than 4TB. This problem has now been fixed.



CR:640955
CR Number:   640955
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3032 10 Sep 2010 Fixed
Description
When using the application profiler and choosing "Overall database performance based on the database schema", a new recommendation has been added when a table definition will slow query execution time. The recommendation is based on a query that will "weigh" the distribution of wide and narrow columns in a table definition (having at least 5 columns) and complain if the majority of wide columns come before the narrow columns.



CR:641068
CR Number:   641068
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3032 13 Sep 2010 Fixed
Description
Tables in UltraLite can now be marked as download-only. Changes to the table on the consolidated database are downloaded during synchronization, but local changes are not sent up to the consolidated database.



Any table with the suffix "_download_only" will be marked as download-only. Tables can also be set to download-only by specifying "SYNCHRONIZE DOWNLOAD" for the sync constraint clause of the "CREATE TABLE" and "ALTER TABLE" SQL statements.



Another related change is that the sync type for a table can only be changed if it doesn't have any unsynchronized changes that need to be uploaded. Previously, the runtime was more permissive in this regard, and changing the type with unsynchronized changes could have unforeseen consequences.



CR:641081
CR Number:   641081
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3012 13 Sep 2010 Fixed
Description
The MobiLink server, and MobiLink and UltraLite clients, now support DER encoded public and private keys. Previously, only PEM encoded keys were supported.



CR:641092
CR Number:   641092
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2582 13 Sep 2010 Fixed
11.0.1 2494 13 Sep 2010 Fixed
10.0.1 4121 13 Sep 2010 Fixed
9.0.2 3985 13 Sep 2010 Fixed
12.0.1 3036 28 Sep 2010 Fixed
Description
The changes for Engineering case 633120, introduced a problem with returning a character string column value when the length of the column value was not bound by the consumer (i.e., the consumer does not provide a pointer to a length field). In this special case, the returned string value should be null-terminated. This has been fixed.



CR:641095
CR Number:   641095
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3037 16 Sep 2010 Fixed
12.0.0 2582 16 Sep 2010 Fixed
11.0.1 2495 16 Sep 2010 Fixed
10.0.1 4122 16 Sep 2010 Fixed
Description
The changes for Engineering case 635618, could have caused an INSERT statement, using the CONVERT() function to convert a string to a time, to fail assertion 111704 - 'Attempting to store invalid time value in table {table name}, column {column name}. This problem did not occur if CAST was used in place of CONVERT, and has now been fixed.



CR:641104
CR Number:   641104
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3036 13 Sep 2010 Fixed
Description
Deployed remote tasks had a context menu item "Initiate...", which when clicked, would have opened a dialog to allow selecting the recipients (agents) for which the task should be initiated. This has been changed th that the menu item is now called "Initiate For All Recipients", and instead of requiring selection of the recipients, it assumes the task on all agents should be initialed. Initiating a task for a single agent, can still be done from the "Recipients" tab in the right pane.



In addition to "Initiate For All Recipients", a new "Cancel For All Recipients" context menu item has been added which requests that the given task be cancelled by all of its recipients.



CR:641111
CR Number:   641111
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2581 13 Sep 2010 Fixed
12.0.1 3033 28 Sep 2010 Fixed
Description
The changes for Engineering case 632640 have been removed, as there were other problems with LOAD TABLE on Mac OS X and Linux systems. Thus for UltraLite, the LOAD TABLE statement is only available via the desktop tools (Interactive SQL utility) on Windows.



Also, while UltraLite accepts the 'ENCODING' load option, it does not perform character set translation: the encoding of the data file must match the database. The preferred method for unloading and reloading UltraLite databases is XML files via the ulunload and ulload tools. Additionally, the ulinit tool is able to load schema and data directly from a SAS database.



CR:641123
CR Number:   641123
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2584 14 Sep 2010 Fixed
11.0.1 2494 14 Sep 2010 Fixed
12.0.1 3036 28 Sep 2010 Fixed
Description
If a mirror or read-only copy node server was shut down while updates were being made on the primary server, the mirror or copy node could have failed to restart. Starting a mirror or copy node while updates were being made on the primary server could also have prevented that server from starting. These problems have been fixed.



CR:641131
CR Number:   641131
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3039 16 Sep 2010 Fixed
12.0.0 2583 16 Sep 2010 Fixed
11.0.1 2496 16 Sep 2010 Fixed
10.0.1 4123 16 Sep 2010 Fixed
Description
When connected to a database using an ODBC data source which used the ASA 9.0 ODBC driver, the Interactive SQL utility could have crashed if an INPUT statement was executed which processed TIME, DATE, or TIMESTAMP data. This has been fixed.



CR:641265
CR Number:   641265
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2582 14 Sep 2010 Fixed
12.0.1 3030 28 Sep 2010 Fixed
Description
The left pane header now contains an icon to help clarify which toolbar button represents the left pane view.



CR:641268
CR Number:   641268
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3026 14 Sep 2010 Fixed
Description
The command editor for a remote task could have been inadvertently closed if the property sheet for the remote task was opened, then OK was clicked. This has been fixed.



CR:641274
CR Number:   641274
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3037 16 Sep 2010 Fixed
12.0.0 2582 16 Sep 2010 Fixed
Description
When running the Deployment wizard, specifying an invalid directory when prompted for the current SQL Anywhere install location, or specifying a non-existent directory for the target directory, would have caused the Deployment wizard to crash. This has been corrected.

Aa valid location must now be specified for your current SQL Anywhere install, and moving past the location pane in the wizard is prevented until a valid location is given. If a non-existent directory is given for the target directory, it will be created.



CR:641276
CR Number:   641276
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2582 15 Sep 2010 Fixed
12.0.1 3037 28 Sep 2010 Fixed
Description
If a SYNCHRONIZE command was canceled before the server could load the dbmlsynccli12 library, it was possible for the server to have crashed. This has now been fixed.





--------------------------------------华丽的分割线-------------------------------------------------------------------------

Sybase SQL Anywhere数据库恢复工具ReadASADB:

之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具: ReadASADB。
此工具支持ASA v5.0, v6.0, v7.0, v8.0, v9.0, v10.0, v11.0, v12.0, v16.0, v17.0等版本。
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具。
恢复Sybase SQL Anywhere的工具在国内处于领先水平。

Sybase SQL Anywhere数据库恢复工具ReadASADB功能
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具
  1. 适用于所有的SQL Anywhere版本    包括:5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x,16.x,17.x
  2. 适用于所有的UltraLite版本
  3. 能够恢复出来表结构和数据
  4. 能够恢复自定义数据类型
  5. 能够恢复存储过程等对象的语法
  6. 能够导出到目标数据库
  7. 能够导出到SQL文件并生成导入脚本
  8. 支持多种字符集,包括:cp850、cp936、gb18030、utf8等
  9. 能够恢复未加密或者简单加密类型的数据
  10. 简单易用
  11. 限制:不支持AES加密的数据文件
请参考:研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具
            SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍

Sybase SQL Anywhere数据库恢复工具ReadASADB适用场景

各种误操作:

  1. 误截断表(truncate table)
  2. 误删除表(drop table)
  3. 错误的where条件误删数据
  4. 误删除db或log文件
  5. 误删除表中的字段

Sybase SQL Anywhere数据库恢复工具ReadASADB的应用场景:

1.因为物理磁盘故障、操作系统、系统软件方面或者掉电等等原因导致的Sybase SQL Anywhere数据库无法打开的情况;
2.误操作,包括truncate table,drop table,不正确的where条件导致的误删除等;
Sybase SQL Anywhere无法打开时,比较常见的错误是:Assertion failed。
如:
1、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Checkpoint log: invalid bitmap page -- transaction rolled back
2、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Page number on page does not match page requested -- transaction rolled back
3、Internal database error *** ERROR *** Assertion failed:200502 (9.0.2.2451) Checksum failure on page 23 -- transaction rolled back
4、File is shorter than expected
5、Internal database error *** ERROR *** Assertion failed: 201116 Invalid free list index page found while processing checkpoint log -- transaction rolled back
6、*** ERROR *** Assertion failed: 51901 Page for requested record not a table page or record not present on page
7、*** ERROR *** Assertion failed: 201417 (7.0.4.3541) Invalid count or free space offset detected on a table page
8、Internal database error *** ERROR *** Assertion failed: 201425 (8.0.3.5594) Invalid count or free space offset detected on a free list page -- transaction rolled back.
9、Internal database error *** ERROR *** Assertion failed: 100702 (8.0.1.2600) Unable to modify indexes for a row referenced in rollback log -- transaction rolled back


-------------------------------------------------------------------------------------------

Sybase ASE数据库恢复工具READSYBDEVICE:

一个不依赖数据库管理系统、直接从Sybase数据库设备文件上提取数据的业内领先的恢复工具!
能够从损坏的Sybase ASE设备文件(.dat)上提取数据的非常规恢复工具。

Sybase ASE数据库恢复工具READSYBDEVICE的主要功能:

  1. 被勒索病毒加密数据文件及备份文件情况下的恢复;
  2. 系统崩溃只剩下数据文件的情况下的恢复,甚至数据库文件不存在而只有损坏的备份文件情况下的恢复;
  3. 因断电、硬盘坏道等造成数据库文件损坏情况下的恢复;
  4. delete数据恢复、误update数据恢复、误删除表(drop)恢复、误truncate表恢复 等;
  5. 各种Sybase内部系统表损坏、索引错误的修复;
  6. master数据库损坏而无法正常运行情况下的恢复;
  7. Sybase数据库被标记为可疑,不可用等情况的恢复;
  8. Sybase数据库中数据文件内部出现坏块情况下的恢复;
  9. Sybase数据库无数据文件但有日志文件的情况下的恢复;
  10. Sybase数据库只有数据文件无任何日志文件的情况下的恢复;
  11. Sybase数据文件被误删除情况下的碎片提取恢复;
  12. 磁盘阵列上的Sybase数据库被误格式化情况下的数据库恢复;
  13. 数据库sysobjects等系统表损坏无法正常应用情况下的恢复;
  14. Sybase数据库还原数据库出现失败情况下的恢复;
  15. Sybase数据库只剩下损坏的备份文件情况下的恢复。

Sybase ASE数据库恢复工具READSYBDEVICE支持的版本:

Sybase ASE 11.0.x,11.5.x,11.9.x,12.0.x,12.5.x,15.0.x,15.5.x,15.7.x,16.0.x


-------------------------------------------------------------------------------------------

SQL Server数据库恢复工具SQLRescue:

一个不依赖数据库管理系统、直接从SQL Server数据库文件上提取数据的业内领先的恢复工具!
能够从损坏的SQL Server数据库文件(.mdf)上提取数据的非常规恢复工具。

SQL Server数据库恢复工具SQLRescue的主要功能:

  1. 系统崩溃只剩下数据文件的情况下的恢复,即无日志文件或者日志文件损坏情况下的恢复;
  2. 断电导致数据库文件损坏情况下的恢复;
  3. 硬盘坏道造成数据库损坏情况下的恢复;
  4. 数据文件内部存在坏页情况下的恢复;
  5. 企业管理器误删除数据表记录,管理软件误删除数据表记录的恢复;
  6. 并闩锁错误、格式化、误删除后导致软件不能使用的情况;
  7. 无法读取并闩锁页sysindexes失败情况下的修复;
  8. 数据文件被误删除情况下的碎片提取恢复;
  9. 系统表损坏、索引错误、误删除数据库表、删除记录的数据找回;
  10. master数据库损坏而无法正常运行情况下的恢复;
  11. 数据文件无法附加情况下的数据恢复;
  12. 数据库被标记为可疑,质疑,不可用等情况的恢复;
  13. 数据库sysobjects等系统表损坏情况下的恢复;
  14. 数据被误(drop、delete、truncate)删除表数据的恢复,误update后的数据恢复等;
  15. 还原时报一致性错误,错误823等情况下的数据恢复,各种错误提示的数据库文件修复;
  16. 数据库被误格式化等情况下的数据库恢复;
  17. 日志收缩造成数据库损坏情况下的恢复;
  18. 仅剩损坏的备份文件情况下的恢复。

SQL Server数据库恢复工具SQLRescue技术特点:

只要SQL Server数据库的数据文件存在,我们就有办法帮您从数据文件中找回重要数据。
  1. 从数据文件中直接恢复数据
  2. 不能附加时直接恢复数据并生成新的数据库
  3. 系统表损坏的数据库修复
  4. 快速修复SQL 823错误、连接中断错误

SQL Server数据库恢复工具SQLRescue支持的版本:

Microsoft SQL Server 7.0, 2000, 2005, 2008, 2008R2, 2012, 2014, 2016, 2017,2019。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------