SysTools SQL Transaction Log Reader 5.0 : Know What is New

The SQL Transaction Log reader is a standalone utility, which helps to view SQL server transaction log files without any difficulty. It is capable enough to preview LDF activity, including Transaction, Time, Name, Query and Table Name.

Moreover, it allows a user to fetch and display all records from the live database. This application offers an option to filter and export as SQL database, as SQL script or CSV file format. It supports to analyze one or more NDF data files without losing a single bit of data. Also, it is compatible with all latest Windows versions, including Windows 10 and its below versions.

SQL Transaction Log reader Tool: Demo vs Licensed

The SQL Log viewer is available in two different versions i.e., Demo and Licensed Version. Let us have a look:

  • Demo Version: The demo version of the software is freely available for download and supports to preview of SQL Server Transactions (INSERT, UPDATE, DELETE), preview Login users that has made changes on database tables, transaction Query, Time. But, doesn’t allow to export Transaction details for recovery purpose.
  • Licensed Version: The licensed version of SQL Transaction Log reader tool permit users to preview all the records within the database. Moreover, it can open and read the complete log activity in SQL server database. Also, it allow you to export all tables data along with deleted records direct in SQL Server Database or SQL Server Compatible script or CSV format.

The Demo version of this SQL Log Recovery available for download in SysTools Group Official Website

Preview SQL Logs

What is New Added in SQL Log Reader Tool to Explore LDF

  1. Allows to View Multiple LDF Files: SQL LDF File Viewer permits you to open and read multiple transaction log files activity in single go. For this, you just need to add parent .ldf file of your database, if you are scanning with offline option. The software will scan and preview transaction activities of all other .ldf database files of that database.
  2. Analyze Same record Update
    Multiple Times and then Delete: SQL log file reader allow you to preview the transactional activity of same record (Updated multiple times and then Delete). This will allow users to track all the database changes for a specific record.
  3. Auto Fetch SQL Server Name: While scanning the transaction logs of a specific database with Online DB option,The SQL transaction log reader tool will allow you to click on drop-down button to auto fetch the Server Name. In case, the software doesn’t shows the desired Server Name, then you can enter it manually.

Existing Features of SQL Log Viewer

  1. Preview All Transaction Records: SQL Server log file viewer scans and load all available tables transactional activities, present in SQL database and creates a preview. It will help to view SQL transaction log file with fields such as Transaction, transaction time, Table name and query. Users can view all records with Login Name Authentication for Insert, Delete, Update etc.
  2. Option to Sort LDF File Elements: The sorting option is available within SQL Log viewer to re-arrange the order of the listed items. Moreover, users can sort each element according to their properties such as transaction, transaction name, transaction time, table name, and query.
  3. Scan with Online or Offline Options: The SQL log file viewer offers two different scanning options to read transactional activities of your database. The Online option asks for SQL Server information like: Server Name, Authentication Type. In Offline option, the software will allow you to browse .ldf file along with its associated .mdf file and preview the transaction log activities.
  4. Export Selective Tables: While moving the SQL LDF file queries, you can check or uncheck all tables for saving only selected data. If you want to restore SQL Log file data from the desired table, then, select and export the desired tables direct to SQL Server Database or SQL Server compatible script or CSV format.

Technical Description of SQL Server LDF Reader Tool

Processor Intel® Pentium® 1 GHz processor (x86, x64) or equivalent
Support RAM Around 2GB (gigabyte) of RAM
Hard Disk Storage Space Minimum 100 MB space for installation
Operating System Windows 10 & all below editions

Final Verdict

After considering the overall functionality of the software, we can summarize that SQL Transaction Log Reader is a reliable tool that allows a user to read and view multiple .ldf files. The software is capable enough to view SQL transaction log with fields such as Transaction, transaction time, Table name and query. Regardless, we can say that the SQL log Viewer is a robust software due to its great features.

SQL Server Latest Updates (Feb. 2018)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2014 SP2, 2016 SP1 and 2017 RTM:

Cumulative Update #4 for SQL Server 2017 RTM

Cumulative Update #10 for SQL Server 2014 SP2

Cumulative Update #7 for SQL Server 2016 SP1

…Stay Tuned! 🙂

SQL Server Latest Updates (Dec. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2014 SP2:

Cumulative Update #9 for SQL Server 2014 SP2

Happy new year and…

…Stay Tuned! 🙂

SQL Server Latest Updates (Nov. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2016 RTM and SP1 and 2017 RTM,:

Cumulative Update #2 for SQL Server 2017 RTM

Cumulative Update #9 for SQL Server 2016 RTM

Cumulative Update #6 for SQL Server 2016 SP1

Starting from this month, we finally get AdventureWorks on github! The direct location is https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks

Stay Tuned! 🙂

SQL Server Latest Updates (Oct. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2017 RTM, 2014 and 2012:

Cumulative Update #1 for SQL Server 2017 RTM

Cumulative Update #8 for SQL Server 2014 SP2

Last but not least, welcome the SQL Server 2012 Service Pack 4!

Stay Tuned! 🙂

SQL Server Latest Updates (Sep. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2016 RTM & SP1:

Cumulative Update #5 for SQL Server 2016 SP1

Cumulative Update #8 for SQL Server 2016 RTM

Starting with SQL Server 2017, the SQL Server releases will follow the Modern Servicing Model, read more here.

Stay Tuned! 🙂

Best Solutions to Repair Suspect Database in MS SQL Server

To repair Suspect database error in MS SQL 2005, 2008, 2012, 2014, 2016 and 2017 read this article to recover SQL Server database from Suspect mode.

What is Suspect Database Error?

Microsoft SQL Server serves as a storehouse for data that is needed for different software applications on a single system or across a network. Sometimes a user may face a situation where a database in the SQL Server instance currently under running state is marked as Suspect. This condition will lead to a failure in creating a connection with the database. Such a database which is tagged as Suspect can be accessed by removing the causes for this problem. The forthcoming article will discuss the causes for this problem to occur and the possible solutions to repair suspect database from SQL Server 2005, 2008, & 2012.

The error message shown to user is somewhat similar to the one given below

Starting up database ‘abc_d’.
Error: 9003, Severity: 17, State: 5.

The log scan number (189623:15:2) passed to log scan in database ‘abc_d’ is not valid.

The above-mentioned error shows that there is some corruption of the log file(.ldf) and does not adhere to the data file(.mdf). Other error messages can also be shown depending upon the cause due to which the database has been categorized as Suspect.

User queries help in getting a better idea about the problem and to recover SQL database.

“I am currently using SQL Server 2008 edition on my Windows 7 system and there are many applications of mine that are dependant on it. Recently I have been facing difficulties in connecting my applications to some of my Databases and they are being shown as Suspect. Kindly guide me to recover SQL database from Suspect mode.”

SQL Server Database Shown as Suspect: Possible Reasons

There are a number of reasons why SQL Server marks a particular Database as Suspect.
Some of these reasons are mentioned as follows

  • Corruption present in the SQL Server Database
  • Insufficient space available to SQL server to repair suspect database during startup.
  • The files of Database are in use by OS or other Backup software
  • Sudden SQL Server Shutdown, Hardware or Power Failure

There exist a number of techniques for solving the issue of Suspect SQL database and broadly they can be classified as Manual and Automated. The upcoming section will try and explain a Manual technique for achieving this goal.

Quick Tip: If you want to skip the tedious & complex manual approach then it is highly advised to use an automatic tool such as SQL Recovery to efficiently recover SQL database from Suspect mode

Repair Suspect Database Manually

Implement the steps given below to recover Suspect SQL Server Database and to access important data.

1. Bring Database in Emergency Mode using the following code

USE master
GO

ALTER DATABASE abc_d SET EMERGENCY
GO

2. Execute DBCC CHECKDB command.
This will scan and check the physical and logical integrity of objects present in the marked database

DBCC CHECKDB (abc_d )
GO

3. Bring the Database in Single Mode using the below-mentioned query

ALTER DATABASE abc_d SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO

4. After the Database is in Single Mode, execute the following code to repair suspect database

DBCC CHECKDB (abc_d, REPAIR_ALLOW_DATA_LOSS)
GO

5. Lastly, restore Multiple access to the database by executing the query

ALTER DATABASE abc_d SET MULTI_USER
GO

Repair Suspect Database by Manual Method: Shortcomings

  • Manual solution consumes a lot of the users’ time for SQL server suspect database repair
  • High risk of losing data forever during manual approach to recover SQL database from suspect mode
  • A Large number of queries to recover SQL database make it complex for non-technical users.
Conclusion

The Suspect database problem is a common issue faced by users of SQL Server database and it has various causes. There is a set of TSQL commands to overcome this error but it poses many issues during implementation. It is better to use automated tools designed specifically for this purpose to repair suspect database.