Monthly Archives: June 2015

SQL Recovery Software for Microsoft SQL Server Database

SysTools SQL Recovery software  is a Windows based solution that specializes in recovering data from MDF and NDF files. The software is small sized, works with basic system requisites, and is integrated with varied features that supports customization of recovery procedure as per user requirement. The product is quite promising for its quality to restore all components of SQL database that includes views, tables, stored procedure, functions, keys, etc. Its ability

Available Options and Capabilities:

  • Table records that were deleted from SQL database can be recovered with the tool. Table recovery from both primary and secondary DB is supported.
  • The scanned copy of corrupted MDF or NDF file can be saved into .str file. If the same data has to be processed by the tool, the .str file can be added.
  • Works on SQL databases that cannot be fixed using built-in commands and tools. Recovers data from system databases that have intense corruption problem.
  • SQL variables or columns that that are created in XML can be recovered with the software.

Detailed Functionality of Tool:

The SQL database recovery tool has some highly beneficial attributes that makes the recovery process absolutely swift for the users. Let us have a discussion over them to know the tool better.

1) Dual Options for Scanning SQL Database: The software is integrated with two options for scanning the selected MDF and NDF files. One is Quick Scan that is for faster recovery of data from the file and another is the Advance scan that is recommended to be chosen for accurate scanning and recovery results.

 

Dual Options for Scanning SQL Database

Dual Options for Scanning SQL Database

2) Preview Components of Database on Screen: After recovery of SQL primary and secondary database, the software will give a preview of all of its items. Tables, triggers, views etc. can be checked out by expanding the hierarchical structure which is similar to object explorer of SSMS.

Preview Components of Database on Screen

Preview Components of Database on Screen

3) Export Recovered Data Accordingly: Once the data is recovered with the tool, it can be exported into SQL Server or into SQL compatible scripts. Any of the option can be selected according to convenience:

Export to Live SQL Server: If SQL Server is available, then database can be directly exported into it. For utilizing this option, the name of server, username, and password (according to authentication) has to be provided.

Export as Compatible Scripts: In case live SQL Server is not available, then in that case the recovered database can be saved into compatible scripts that can be saved on local machine.

Export Recovered Data Accordingly

Export Recovered Data Accordingly

4) Database Export with or without Schema: If the underlying schema of the database has to be exported along with the database, then this can be made possible with the tool. There is optional facility in the tool for exporting the recovered database without or with its schema.

Database Export with or without Schema

Database Export with or without Schema

5) Restore Deleted Records from Table: If records from SQL database are deleted, then they can be recovered and exported. While the software is instructed to export the database, it prompts for user permission for exporting the records that have been deleted from tables.

Restore Deleted Records from Table

Restore Deleted Records from Table

I tested a trial recovery of my database and it turned out pretty well and am planning to publish a video blog of it in the future.

Overall, I would like to give SQL Recovery 4 stars out of 5.

The software works for all versions of SQL Server: 2000, 2005, 2008, 2012, and 2014. In addition to this, export to all latest editions is supported. 

Download and Purchase:

The product is available for trial and its license can be purchased from official website of the product: http://www.systoolsgroup.com/sql-recovery.html

Creating a SSRS report to show SSIS package run time statistics

In most companies developers are restricted from accessing the MSDB database and they rarely know the performance of their packages in a production environment unless they have access to third party software tools or a friendly DBA. This happened to me once when I wanted to know how long my packages ran in a production environment and I had no access to the MSDB database to look at the sysjobs and sysschedules tables. The work around is to enable SQL Server logging in SSIS packages and to create a SSRS report from the sysssislog table.

The logic behind this solution is to enable SQL Server Logging in SSIS packages while we create/develop the package and send it for deployment.

Follow the rest of the article from here