A Review of Stellar Phoenix SQL Database Repair

SQL Server is a database server developed by Microsoft, the primary function of which is to store and retrieve data in the database MDF and NDF files. It retrieves data as requested by several software applications running on same or different computer across a network. Plus, it has a lot of concurrent users. Aimed at various enterprise segments, it caters to different workloads ranging from a small single-machine to large Internet-facing applications.

Although data on it is stored in a safe and secure manner, yet there are instances when it’s MDF and NDF files get damaged or turns inaccessible due to one or more reasons. Moreover, this happens irrespective of the SQL Server versions that can be 2016, 2014, 2012, 2008, etc. When they get damaged, they come up with several and unique error messages. Such a situation restricts you from accessing the stored data of the database. This creates the necessity for using a third-party software that can repair both these files and extract the complete data out of it. Here, Stellar Phoenix SQL Database Repair would serve the purpose. Let’s look at how.

Developed and marketed by Stellar Data Recovery, Stellar Phoenix SQL Database Repair is a software the purpose of which is to repair the damaged or corrupt MDF and NDF files of Microsoft SQL Server and save all the extracted data in multiple formats such as MS SQL, HTML, XLS and CSV. Here, we present to you a review on this product for you to get in-depth details about it. With this, you can check whether the software achieves your purpose of perfectly repairing the database files and recovering the entire data; and, that whether you can use it in case the primary MDF and secondary NDF files of the SQL Server database gets damaged or turns corrupt.

First, it is imperative to acquaint with its salient features as well as benefits. Let us look at the features and benefits embedded in the software.

Features & Benefits:

· It can repair the damaged or corrupt MDF and NDF files of your SQL Server database.
· It can search for MDF files on the PC and repairs it successfully.
· It can retrieve almost all the database components ranging from Tables, Triggers, Views, Rules, Keys, Indexes, to Defaults.
Note - The Keys that can be recovered are Primary Keys, Unique Keys, Foreign Keys, and Identity, while the Indexes that can be recovered are both Clustered as well as Non-clustered indexes.
· It can recover both ROW and PAGE compressed data of the SQL Server database files.
· It has an exceedingly fast Scan feature with which you can scan the damaged MDF and NDF files.
Note - With this, you can identify and fix the issues quickly and recover all the data objects without fail.
· It allows you to preview the objects that can be retrieved and appear as a scan result after the end of the scanning process.
· It connects to the server automatically when interrupted for completing the repair process and restoring the data.
· It can even recover the Deleted records by using the remarkable feature embedded in the software.
· It offers you the option to move and save database files to Live SQL Database after the repair process gets over.
· It gives you the option to save the fixed database files in multiple formats such as CSV, XLS, and HTML in addition to MS SQL.
· It supports the latest released version i.e. MS SQL Server 2016 in addition to lower releases such as MS SQL Server 2014, 2012, 2008, and all others.

Now, to be able to execute these features and avail the benefits of this software when you have a damaged or corrupt MS SQL Server, your system must fulfil minimum system requirements, which are as follows

· The system must be embed with Pentium Class processor only.
· The supported operating system are Windows 10, 8, 8.1, 7, Vista, and XP as well as Windows Server 2008/2003.
· The system must possess a minimum of 1 GB memory; however, the recommended size is 2 GB.
Lastly, the free space in the system hard drive should be at least 50 MB to get the software installed correctly.

Note - These system specifications are easy to achieve and almost all Windows systems possess these minimum system specifications by default.

Working:

The working of the software is described here and takes you through the steps to repair the corrupted MDF & NDF files of MS SQL Server.

Select, Repair, and Save are the three most important steps that you need to carry out with this software to successfully repair the damaged SQL database files.

· Select – As displayed in the image below, with the ‘Select Database’ option that is present in the interface of the tool; you need to select the damaged database file from any location in your system. However, if you do not know the same, you must use the ‘Search in Folder’ and ‘Find’ tab to search and find all the database files. If you want to locate the file in subfolders as well, you must mark the option ‘Search in subfolders.’ Further, to scan for and recover the deleted records, you must check the ‘Include deleted record’ option.



· Repair – Once you have selected the database MDF file, you must click on the ‘Repair’ button to scan the MDF file. With this, you get a list of all the recoverable objects as shown in the image below. Further, you can select the ones for which you require a preview.



· Save – Finally, there is a message that the selected SQL database file has been successfully repaired, and the software prompts to click on the OK tab to save the file in a new database. This is the third and last step that you have to follow with the software. When you do this, you get options to save the file in MS SQL, HTML, CSV, and XLS that you can select as per your choice. Next, it gives you the option to save in ‘New database’ and ‘Live database’, and again you can choose as per your requirement. Finally, the retrieved objects of the SQL Server database file get saved. The images below display the ‘Saving’ step.

User have four options to save the database.
· MSSQL
· CSV
· HTML
· XLS



After selecting MSSQL, two options are there
· New Database
· Live Database





Choose any options from these two and save the database.

Conclusion:

Now you know the features, system requirements, and working of the Stellar Phoenix SQL Database Repair software, you can analyze the tool and check whether it meets the purpose. A better way to try this utility is to download its demo version. You can then register the software if you find it satisfactory. Given its efficiency in repairing the SQL database file with precision and speed, I would give it an 8.5 on 10.

Continue Reading

How to upgrade your ASP.NET Core application from 1.0 to 1.1

TL;DR;

In this blog, We are going to learn how we can upgrade your ASP.NET Core application from 1.0 to 1.1.  Now Microsoft has release 1.1 before few months, So in this blog, we will see how you can upgrade your ASP.NET 1.0 application to ASP.NET 1.1 core application.

Where to download 1.1 SDK and Tooling for Visual Studio 2015:

You can download 1.1 SDK and Tools from the following link.

https://www.microsoft.com/net/download/core?tduid=(42c8fb30096a508e70a0e7f0d6bdaf55)(256380)(2459594)(TnL5HPStwNw-1.6L2HANlqPr5.uZiHJ1MQ)()#/current



Here different tooling is also available for the Visual Studio 2015 and Visual Studio 2017. For this blog post, We are going to use Visual Studio 2015.

How to upgrade to ASP.NET core 1.0 to ASP.NET core 1.1:

So let’s get started. I’m going to create a new ASP.NET Core 1.1 application and then we will move it to ASP.NET 1.1. So let’s create an ASP.NET core 1.0 application and then let’s upgrade it to 1.1. I have created a new application like following.



Once you click ok it will have a dialog selecting application type and I’m going to select web application.



Once you click Ok, It will create an application like below and you can see that it’s an ASP.NET Core 1.0 application.



And here’s how it’s project.json looks like.

{
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.1",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Diagnostics": "1.0.0",
    "Microsoft.AspNetCore.Mvc": "1.0.1",
    "Microsoft.AspNetCore.Razor.Tools": {
      "version": "1.0.0-preview2-final",
      "type": "build"
    },
    "Microsoft.AspNetCore.Routing": "1.0.1",
    "Microsoft.AspNetCore.Server.IISIntegration": "1.0.0",
    "Microsoft.AspNetCore.Server.Kestrel": "1.0.1",
    "Microsoft.AspNetCore.StaticFiles": "1.0.0",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.0.0",
    "Microsoft.Extensions.Configuration.Json": "1.0.0",
    "Microsoft.Extensions.Logging": "1.0.0",
    "Microsoft.Extensions.Logging.Console": "1.0.0",
    "Microsoft.Extensions.Logging.Debug": "1.0.0",
    "Microsoft.Extensions.Options.ConfigurationExtensions": "1.0.0",
    "Microsoft.VisualStudio.Web.BrowserLink.Loader": "14.0.0"
  },

  "tools": {
    "BundlerMinifier.Core": "2.0.238",
    "Microsoft.AspNetCore.Razor.Tools": "1.0.0-preview2-final",
    "Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.0.0-preview2-final"
  },

  "frameworks": {
    "netcoreapp1.0": {
      "imports": [
        "dotnet5.6",
        "portable-net45+win8"
      ]
    }
  },

  "buildOptions": {
    "emitEntryPoint": true,
    "preserveCompilationContext": true
  },

  "runtimeOptions": {
    "configProperties": {
      "System.GC.Server": true
    }
  },

  "publishOptions": {
    "include": [
      "wwwroot",
      "**/*.cshtml",
      "appsettings.json",
      "web.config"
    ]
  },

  "scripts": {
    "prepublish": [ "bower install", "dotnet bundle" ],
    "postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
  }
}

And here’s how the global.JSON looks like.

{
  "projects": [ "src", "test" ],
  "sdk": {
    "version": "1.0.0-preview2-003131"
  }
}

So the first thing we need to is to upgrade the global.json to latest version like below.

{
  "projects": [ "src", "test" ],
  "sdk": {
    "version": "1.0.0-preview2-1-003177"
  }
}

So here in project.json, you can see that all packages belong to 1.0. Now there is multiple ways we can do upgrade either we can manually upgrade all packages via manually upgrading it or we can do it with Visual Studio tooling. I’m going to use Visual Studio tooling as that is the easiest way to do it. You can do this via Right Click your application and Select “Manage Nuget Packages for this solution”. It will load the following dialog. You need to goto Update tab of that dialog.



You need to select upgrade all packages and update your application. Once you did with that there is once place where you need to manually upgrade it in project.json. GoTo following part of project.json.

"frameworks": {
  "netcoreapp1.0": {
    "imports": [
      "dotnet5.6",
      "portable-net45+win8"
    ]
  }
},

Now upgrade netcoreapp1.0 to 1.1 like below.

"frameworks": {
  "netcoreapp1.1": {
    "imports": [
      "dotnet5.6",
      "portable-net45+win8"
    ]
  }
},

Now once you do that and build your application. You might get the error like following.



That is because of windows runtime is not there for 1.1. So you need to add following in project.json.

"runtimes": {
  "win10-x64": {}
},

Now once you add that in project.json. It will restore the runtime for your operating system and it will start building your application.
And here’s how my project.json looks like after upgrading all stuff.

{
  "dependencies": {
    "Microsoft.AspNetCore.Razor.Tools": {
      "version": "1.0.0-preview2-final",
      "type": "build"
    },
    "BundlerMinifier.Core": "2.2.306",
    "Microsoft.Extensions.Logging": "1.1.0",
    "Microsoft.Extensions.Logging.Console": "1.1.0",
    "Microsoft.Extensions.Logging.Debug": "1.1.0",
    "Microsoft.Extensions.Options.ConfigurationExtensions": "1.1.0",
    "Microsoft.NETCore.App": "1.1.0",
    "Microsoft.VisualStudio.Web.BrowserLink.Loader": "14.1.0",
    "Microsoft.AspNetCore.Diagnostics": "1.1.0",
    "Microsoft.AspNetCore.Mvc": "1.1.1",
    "Microsoft.AspNetCore.Routing": "1.1.0",
    "Microsoft.AspNetCore.Server.IISIntegration": "1.1.0",
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.AspNetCore.StaticFiles": "1.1.0",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.1.0",
    "Microsoft.Extensions.Configuration.Json": "1.1.0"
  },

  "tools": {
    "Microsoft.AspNetCore.Razor.Tools": "1.0.0-preview2-final",
    "Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.0.0-preview2-final"
  },

  "frameworks": {
    "netcoreapp1.1": {
      "imports": [
        "dotnet5.6",
        "portable-net45+win8"
      ]
    }
  },

  "buildOptions": {
    "emitEntryPoint": true,
    "preserveCompilationContext": true
  },

  "runtimeOptions": {
    "configProperties": {
      "System.GC.Server": true
    }
  },


  "publishOptions": {
    "include": [
      "wwwroot",
      "**/*.cshtml",
      "appsettings.json",
      "web.config"
    ]
  },

  "runtimes": {
    "win10-x64": {}
  },

  "scripts": {
    "prepublish": [ "bower install", "dotnet bundle" ],
    "postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
  }
}

And in solution explorer, you can see that now it’s targeting to 1.1.



That’s it. It’s pretty easy to upgrade your application to latest build. Hope you like it. Stay tuned for more!!

Continue Reading

How to upload file with Express,Pug and Multer in Node.js

TL;DR;

In this blog post, We are going to learn how to upload a file with Express, Pug, and Multer in Node.js. In this blog post, we will learn how we can upload file with multer middleware in express framework with node.js

Creating Express App, Multer and other common code:

So here in for the demo purpose, we are going to use express application. So here is our package.json for express framework node.js application. It is created via the express generator. I have added Multer and PUG NPM instead of Jade.

{
  "name": "nodejsfileupload",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "start": "node ./bin/www"
  },
  "dependencies": {
    "body-parser": "~1.15.2",
    "cookie-parser": "~1.4.3",
    "debug": "~2.2.0",
    "express": "~4.14.0",
    "morgan": "~1.7.0",
    "multer": "^1.2.1",
    "pug": "2.0.0-beta6",
    "serve-favicon": "~2.3.0"
  }
}

Here in the above code, You can see that there are pug npm and multer npm. Once you do “NPM Install” it will install all the required NPM for the same. Now we are our standard express app ready and here’s how our structure looks in visual studio code.

What is Multer:

For those who don’t know what is Multer,

Multer is a node.js middleware for handling multipart/form-data, which is primarily used for uploading files. It is written on top of busboy for maximum efficiency.

It is a middleware that will help you handle multipart/form-data requests and you can upload the file with that middleware with some configuration code.You can find more information about Multer at - https://github.com/expressjs/multer

Common code for Multer:

Now once we are done with Installing node module, It’s time to write some common code for Multer middleware. Here in the above code, we are going to use the index.js router which is a default router for the express app.  The index.js code looks like following.

var express = require('express');
var router = express.Router();

//multer object creation
var multer  = require('multer')
var storage = multer.diskStorage({
    destination: function (req, file, cb) {
        cb(null, 'public/uploads/')
    },
    filename: function (req, file, cb) {
        cb(null, file.originalname)
  }
})

var upload = multer({ storage: storage })

/* GET home page. */
router.get('/', function(req, res, next) {
  res.render('index', { title: 'Express' });
});

router.post('/', upload.single('imageupload'),function(req, res) {
  res.send("File upload sucessfully.");
});

module.exports = router;

Here in the above code, you can see that first I’m creating a multer object with require syntax and then I have put some configuration with multer.diskstorage. Basically, It's said that we are going to store the uploaded files into public/uploads folder and the name of a file will be same which we uploaded. Then in post request, you can see that I have put “upload.single” which handle file upload with post request. And if it uploaded successfully, I’m sending a response back that file is upload successfully.

HTML/PUG code:

Following is an HTML code for the pug.

extends layout

block content
  h1= title
  p Welcome to #{title}
  form(method='post', enctype='multipart/form-data')
    input(type='file', name='imageupload')
    input(type='submit', name='uploadimage', value='Upload Image')

Here you can see I have a file upload control with multi-part data and form and submit button to make a post request.

Final Output:

Once you run this application in the browser it will look like following.



That’s it. It’s pretty easy. Hope you like it. Stay tuned for more!.

You can find complete source code following example on Github at - https://github.com/dotnetjalps/NodeJsFileUpload

Continue Reading