中国最专业的商业控件服务网

慧都控件网

电话:400-700-1020(免费)或023-66090381
product
十年的Flash图表经验,十年Fusionchart辉煌
  • 暂时没有相关新闻
上一个 上一个 ApexSQL Debug 下一个 下一个ApexSQL Universal Studio
ApexSQL Log API
[产品编号: 11908 ]  
ApexSQL Log API

收藏订阅

  • 当前版本:v2010.02   [销售以商家最新版为准,如需其他版本,请来电咨询]
  • 开  发 商:ApexSQL 正式授权
  • 产品类型:独立控件
  • 产品功能:数据库相关
  • 控件类型:.NET
  • 其他特性:Web Form / Windows Form
  • 产品源码:不提供源码
关于本产品的分类与介绍仅供参考,具体以商家网站介绍为准。
产品介绍 下载 购买 版本更新 开发商 视频与培训 评论  
ApexSQL Log API v2008.05(最新版) (09-12-31) v2008.03

ApexSQL Log API 版本更新 v2008.05 (更新日期:12/31/2009)

Enhancements:

  • - The following new classes have been added to the API:
           ApexSql.Log.InsertDeleteRowOperation class used between InsertRowOperation and DeleteRowOperation on one hand and DmlLogOperation on the other
  • - The following new methods have been added:
           Utility.CheckSource() method for log sources checks accessibility of a log source
           Utility.CheckSource() and Utility.CheckSources() methods for data sources check accessibility of data sources     
           ServerSideComponentsManager.StartConnectionMonitor() method starts Connection Monitor if it is already enabled
           Database.ProcessServerSideLogMessages() method retrieves server-side logs from the server
           Auditor.StartReversed() method audits operations in backward order; used for UNDO operations
           Config.ConfigureIntermediateFilesPath() method configures path for the intermediate files created during auditing
           RowHistory.GetColumnType() method retrieves Column Type
           ServerSideComponentsManager.EnableConnectionMonitor() method enables Connection Monitor but doesn't start it
           ServerSideComponentsManager.StartConnectionMonitor() method starts Connection Monitor on the server if it is enabled
           ServerSideComponentsManager.StopConnectionMonitor() method stops Connection Monitor on the server
           ServerSideComponentsManager.StopAndDisableConnectionMonitor() method stops and disables Connection Monitor on the server
           ServerSideComponentsManager.DeleteAllConnectionMonitorData() method deletes all login data from APEXSQL_LOGIN, APEXSQL_LOG_CONNECTION_MONITOR_SESSION tables used by Connection Monitor
           ServerSideComponentsManager.InstallComponentsWithDefaultServerLogon() method tries to install server-side components using Windows account that SQL Server is running from
           ServerSideComponentsManager.UninstallComponentsWithDefaultServerLogon() method tries to uninstall server side components using Windows account that SQL Server is running from
           ServerSideComponentsManager.InstallComponentsWithServerLogon() method tries to install server side components using specified Windows account information
           ServerSideComponentsManager.UninstallComponentsWithServerLogon() method tries to uninstall server side components using specified Windows account information
           ServerSideComponentsManager.StartServerHelperWithServerLogon() method starts Server Helper service using specified Windows account information
           ServerSideComponentsManager.StartServerHelperWithDefaultServerLogon() method starts Server Helper service using Windows account that SQL Server is running from
           ServerSideComponentsManager.SetConnectionMonitorCleanupInterval() method sets time interval in seconds which indicates how often data should be purged from APEXSQL_LOGIN, APEXSQL_LOG_CONNECTION_MONITOR_SESSION tables used by Connection Monitor
           ServerSideComponentsManager.GetConnectionMonitorCleanupInterval() methods gets time interval in seconds which indicates how often data should be purged from APEXSQL_LOGIN, APEXSQL_LOG_CONNECTION_MONITOR_SESSION tables used by Connection Monitor
           ServerSideComponentsManager.CheckConnectionMonitorDatabaseName() method checks if specific database can be used by Connection Monitor
           ServerSideComponentsManager.SetConnectionMonitorDatabaseName() method sets database name that should be used by Connection Monitor; Database will not be created
           ServerSideComponentsManager.GetConnectionMonitorDatabaseName() method gets database name that is currently used by Connection Monitor
           ServerSideComponentsManager.SetConnectionMonitorServerLogon() method sets account information under which Connection Monitor is running
           ServerSideComponentsManager.CheckConnectionMonitorServerLogon() method checks if Connection Monitor can run under specified account information
  •  - The following new properties have been added:
           ServerSideComponentsManager.ServerHelperServiceStatus is the current status of Server Helper service
           ServerSideComponentsManager.ComponentsVersion is the version of currently installed Server Side Components
           Field.Type is the SQL type of the field
           Field.Column is the Column object
           Field.ColumnId is the ID number of the column
           Row.Table is the Table object to which the row belongs to
           ServerSideComponentsManager.ConnectionMonitorStatus is the current status of Connection Monitor
           Config.Initialized signals if the API has been initialized
           Transaction.UserIdSid returns SID if it is available or ID of the user that created this transaction
           Transaction.LoginTime returns login time of the connection on which this transaction was created
           Database.Id returns the ID of the database
           Database.FamilyGuid returns family GUI of the database
           Database.Collation returns collation ID of the database
           Database.DateCreated returns database creation date
           Database.KeepConnectionOpen indicates whether database connection should be kept open all the time or be immediately closed after use
  • - The following new exceptions can now be thrown from the API:
           CannotAccessDataSourceException
           InsufficientCredentialsException
           BadConnectionMonitorConfiguration
           ConnectionMonitorErrorException
           InsufficentInstallPermissionsException
           InsufficentExecPermissionsException
  •  - The following new enums have been added:
           ApexSql.Log.ConnectionMonitorAuthentication
           ApexSql.Log.ServiceStatus
  • - Field.GetBinaryStream() method can now return binary stream for any data type not just BLOBs
  • - BLOB reading now consumes less memory (up to 50% less)

Fixes:

  • - It's impossible to connect to SQL Server using Windows Authentication under Vista with active UAC
  • - When a machines' hardware ID changes, the server's activation status becomes invalid and re-activating is not possible
  • - "Unknown SQL Server version" error is thrown when reading SQL Server 2000 backups
  • - Online transaction log files sometimes cannot be accessed on an x86 OS that has more than 4 GB of RAM
  • - SPID values are incorrectly outputted for SQL Server 2008
  • - The application fails when trying to read SQL Server 2000 database backups
  • - Servers with expired evaluation can’t be activated
  • - Online transaction log and database files hosted on Windows 2000 cannot be read
  • - BLOBs whose data type has been changed are outputted incorrectly
  • - UPDATE operations are sometimes not reconstructed correctly even when there is enough data to do so
  • - SMALLMONEY values are outputted incorrectly
  • - Table filters work incorrectly for SQL Server 2000 transaction logs audited under SQL Server 2005/2008
  • - Server Helper service can’t be started correctly if installed over older version of Server-side Components

Changes:

  • -  API now throws ApexSql.Log.Exception instead of System.Exception. ApexSql.Log.Exception inherits System.Exception so no user code needs to be changed
  • -  Server-side components have been split to two independent sets: server-side components for ApexSQL Log and server-side components for ApexSQL Recover. On upgrade, un-used server-side components are deleted.
           Split ApexSqlServerXprocs2008.dll into ApexSqlLog2008Xprocs.dll and ApexSqlRecover2008Xprocs.dll
           Split ApexSqlServerHelper2008.exe into ApexSqlLog2008ServerHelper.exe and ApexSqlRecover2008ServerHelper.exe
           Split ApexSqlServerHelper2008.sys into ApexSqlLog2008ServerHelper.sys and ApexSqlRecover2008ServerHelper.sys
  • - Renamed xp_ApexSqlConnectionMonitor2008* extended procedures to xp_ApexSqlLog2008ConnectionMonitor*
  • - Renamed sp_ApexSqlConnectionMonitor2008* stored procedures to xp_ApexSqlLog2008ConnectionMonitor*
  • - All server-side logs for the application's server-side components are consolidated into one log file: ApexSqlLog2008.log
  • - All application logs, both client and server-side, are now in UNICODE
  • - Evaluation period for each server has been changed from 30 to 14 days
  • - The following methods of ApexSql.Log.ServerSideComponentsManager class have been marked as obsolete:
           ForceStartConnectionMonitor
           DisableConnectionMonitor
           InstallComponents
           UninstallComponents