Site sponsored by: Idera The gold standard of SQL Server performance monitoring & diagnostics.
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • Quiz
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


Product Reviews

All Reviews
Audit Tools
Backup Tools
Change Management Tools
Clustering Tools
Coding Tools
Design Tools
Diff / Compare Tools
Documentation Tools
Job Management Tools
Log Recovery Tools
Monitoring Tools
Remote Access Tools
Reporting Tools
Security Tools
Testing Tools

Write for Us

Share your SQL Server knowledge with others and raise your profile in the community More...
Latest Articles

Recover Data Using Database Snapshots
Analyze and Fix Index Fragmentation in SQL Server 2008
Powerful Geographical Visualisations made easy with SQL 2008 Spatial (Part 2) ...
Backup User Databases Using a Maintenance Plan

More     
 
Latest FAQ's

How to alter a User Defined Data Type?
How to unzip a File in SSIS?
How to view previous query plans?
ALTER TABLE SWITCH statement failed because the object '%.*ls' is not ...

More     
   
Latest Software Reviews

Spotlight on ApexSQL Doc 2008
ApexSQL Enforce
Embarcadero Change Manager
SQL Server DBA Dashboard

More     

reviews >> log recovery tools >> Spotlight on ApexSQL Log : SQL Server ...

Spotlight on ApexSQL Log : SQL Server Audit & Recovery Tool

By : Frank Kalis
Jan 24, 2007

Page 2 / 8

To emphasize this point once again, this whitepaper discusses a typical OLTP environment. I am not talking about OLAP systems, which certainly do have their own set of recommendations and guidelines, but are beyond the scope of this paper. Here are some interesting knowledgebase articles on this topic

How to: Create a Transaction Log Backup (Transact-SQL)
How to: Restore to the Point of Failure (Transact-SQL)
How to: Restore to a Point in Time (Transact-SQL)

Brief introduction into the overall use of ApexSQL Log

Given the above environment, let's explore how to use the software to get familiar with it. After installation and activation, you will see a typical Windows GUI when you start ApexSQL Log:

First thing you must do now, is to add the databases, respectively their logs, which you want to monitor. To add a database, you use the „New Log“ button from the toolbar or select this from the context menu of the Server Explorer.

The then activated wizard guides you safely through the rest of the process

The above screen is self-explaining and you should already be very familiar with it. It's the typical login dialog.

As you can see from the above picture, ApexSQL Log is able to deal with these types of logs:

  • Online logs
  • Backup logs
  • Offline logs


<< Prev Page     Next Page>>    








Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views


              © 1999-2008 by T10 Media. All rights reserved