FAQs - ApexSQL Log API

Yes, you can download it from the ApexSQL Download Page.

The evaluation copy is fully functional. The only restriction is a 30-day evaluation period for any given server instance.

ApexSQL Log API's server-side or API components can be installed using the standalone installer which can be downloaded from the ApexSQL Download Page.

Yes. Both applications use the same server-side components. The versions of ApexSQL Log and ApexSQL Log API need to be the same.

Yes, it has both server and client components. Server components are installed into SQL Server's Binn directory and include one DLL with extended procedures, several executables and one device driver. Client components consist of a single .NET assembly.

Yes, otherwise, the older version of ApexSQL Log or ApexSQL Log API will not work with the server.

There is no update notification mechanism in ApexSQL Log API. To be automatically notified about new ApexSQL Log API updates or versions, you may subscribe to our forum.

You can update by downloading the new version from the Downloads page and installing it over the one you already have. Servers can be updated directly from API (when client and server components are on the same domain and the user who's using the client components has "write" privileges to SQL Server's directories).

ApexSQL Log API supports:

SQL Server 2005 32-bit
SQL Server 2005 64-bit (x64)
SQL Server 2000 32-bit
SQL Server 7.0

For online transaction log reading to work operating system has to be 32-bit versions of Windows 2000 or higher or 64-bit versions of Windows XP x64 or higher. For Itanium (IA64) SQL Server 2000 and 2005 only experimental support is available. Experimental support is also available for all versions of SQL Server 2008.

ApexSQL Log API supports 64-bit versions of Windows XP x64 or higher. For Itanium (IA64) SQL Server 2000 and 2005 only experimental support is available.

No, ApexSQL Log API doesn't support email alerts. However, custom functionality can be built on top of ApexSQL Log API to support email alerting.

You need to get an Activation Key from the Sales (link this to contact page or sales@apexsql.com) department and then call Activate Automatically() method from you project. For more information on how to do this, check out the Activation Section of the Help File.

The License mechanism works per server and not per end-user computer. You need to activate your ApexSQL Log API distributable files on the end-user's server in essentially the same way you activate ApexSQL Log in your development environment. Methods to activate your application on the end-user computer silently are discussed in the ApexSQL Log Help File.

ApexSQL Log API may be used to:

• Leverage ApexSQL's transaction log reading capability in your own applications and be able to track changes done on the database.
• Audit Online, Backup, and Detached data sources.
• Customize audit result output to fit your needs.
• Enhance the capabilities of ApexSQL Log with functionalities such as email alerts, custom reporting, and more.

ApexSQL Log API exposes ApexSQL Log's ability to audit changes made to user or system tables by reading of online, backup or detached transaction logs. Advanced auditing options like DDL auditing or generation of UNDO/REDO statements are not exposed. ApexSQL Log's Recovery options (recovery of deleted, truncated, dropped or otherwise lost data) are also not exposed. If you need any of these functionalities, you can download ApexSQL Log from here.

Yes, you just need to add a reference to the ApexSQL.Log.Api.dll to your solution and distribute all ApexSQL Log API redistributable files with your application. The only limitation is that your application (commercial or otherwise) must not compete with ApexSQL Software products. See the End User License Agreement for more details on this and other provisions.

Yes, the fully functional example is available from the ApexSQL Log API's application directory (ApexSqlLogApiDemo.csproj). A Step-by-step guide on how to start development with ApexSQL Log API can be found in the Help File (Development with ApexSQL Log API)

When distributing ApexSQL Log API with your application, you need to distribute all of these (and only these) files:

ApexSql.Log.Api.dll
ApexSqlLogActivation.exe
ApexSqlLogApiActivation.exe
ApexSqlConnectionMonitor.dll
ApexSqlConnectionMonitorx64.dll
ApexSqlConnectionMonitorIA64.dll
ApexSqlServerXprocs.dll
ApexSqlServerXprocsx64.dll
ApexSqlServerXprocsIA64.dll
ApexSqlServerHelper.exe
ApexSqlServerHelperx64.exe
ApexSqlServerHelperIA64.exe
ApexSqlServerHelper.sys
ApexSqlServerHelperx64.sys
ApexSqlServerHelperIA64.sys

One license of ApexSQL Log API allows you to activate one (1) instance of SQL Server. The client-side or API components, however, can be installed on multiple client servers.

Additional licenses can be purchased from ApexSQL. We have licensing schemes for a small number of additional servers, a larger distribution within the same company/site, and an Enterprise License for Commercial distribution. Please contact sales for pricing.

Yes, please refer to the End User License Agreement for a complete list of license provisions. This is included in the evaluation installer and can also be found on the website.

Yes, ApexSQL Universal Studio will include one license of ApexSQL Log API. ApexSQL Universal Studio customers who are still under maintenance will qualify for a free copy of ApexSQL Log API.