SQL Dumper

Probably most of the developers may be knowing about SQL Dumper.

SQL Server Dumper enables you to dump selected SQL Server database tables into SQL Insert statements, that are saved as local .sql files and contain all the data required to create a duplicate table. It can also be used to backup table data.

You can choose to create an individual .sql file for each table, or combine all selected tables into a single file.

How to use SQL Dumper:
1. Download it from the following official site and install it.


2. Once you open it, you have 2 options. You can use either SQL server authentication or
    windows authentication. I have used SQL server authentication.
    Enter server name, login ID and password and click on connect.

3. Once connected, select database from right hand dropdown. Once selected, it will
    automatically fetch all the tables within that database.

4. Select a table from “available tables” list and it to “tables to dump” list.

5. From “Output settings”, tick the checkbox “Set output file name”, enter the name of the
    backup file without including the extension e.g like Author or tablename etc.

6. Click on “Execute” button, it will show you progress bar on the bottom of the window. Once
   done, browse the script file.

To conclude:
SQL Dumper is very handy utility for developers. Please try and let me know what do you
think on this.

State Management In ASP.NET


Since HTTP is stateless protocol, all information associated with the page and the controls on the page would be lost with each round trip between client to server.

To overcome this limitation, ASP.NET includes several options that help you preserve data on page basis and an application basis.

There are basically 2 types of state management in ASP.NET:

  1. Server side state management
  2. Client side state management

Server side state management:

Session State:

Session state is stored in the Session key/value dictionary. Session is maintained per               user. You can save session either in-proc, on state server or on SQL server which can be         configured through web.config file.

Application State:

Like session state does, an Application state is also stored in a key/value dictionary that is     created during each request to a specific URL.

ASP.NET provides 3 events that resides in Global.asax which enable you to handle           application events namely Application_Start, Application_End and Application_Error.

Client side state management:

View State:

This saves all the values of the controls from the page on the webpage between a page         request. This means, viewstate of 1 page can not be accessible in some other                     page (Latest version of .net framework supports accessing viewstate of 1 page into some other page). When the page is processed, the current state of the page is hashed into a string and saved in the page as a hidden field.

Control State:

You may know that viewstate can be disabled from page. But suppose if we are working on a control and need to store control-state data in order for a control to work properly. In such cases, if we disable viewstate from the page, control will not function properly. To overcome this, control state is introduced. The Control State property allows you to persist property information that is specific to a control and cannot be turned off like the ViewState.

Hidden Fields:

ASP.NET allows you to store information in hidden fields. We can see value of a hidden field by viewing the HTML source code of a page. Since hidden fields are stored in plain text, it is recommended not to store sensitive information in it.


A cookie is just a plain text file, used by a browser & server to read and write values from it. We can store a small pieces of information in it. Again as it is a plain text file, it is recommended not to store sensitive information in it as user can manipulate it.

Query Strings:

A query string is data/information that is appended to the end of a page URL. It can be used to pass information from one page to another to even in the same page. It provides a simple but limited way to maintain state information as some browsers/client devices impose a 2083 character limit on the length of the URL. Since querystring is exposed to user, it is recommended not to store sensitive information in it.

What Is Common Language Runtime (CLR) ?

Common Language Runtime (CLR):

  • CLR Stand for Common Language Runtime.
  • It is called a heart of .NET framework.
  • It provides runtime environment for .NET languages.

CLR has following responsibilities:

  1. Intermediate language (IL) to native translation:                                                             CLR uses Just In Time (JIT) compiler which compiles IL code to machine code. This machine code then executed under .NET framework.
  2. Code Verification:                                                                                                                    It provides type safety while code executes. It prevents the source code from performing illegal operations. e.g If source code is accessing invalid memory, CLR prevents it.
  3. Code Access Security (CAS):       
    Responsibility of this is to grant rights to programs depending upon the security configurations of the system.
  4. Garbage Collection (GC):                                                                                                       Basic responsibility of this is memory management. Thus we can code a program without need to think about how to release a memory allocated by an object. GC automatically releases memory of an object which are not referred any more by a program.

Step By Step Installing Visual Studio Professional 2012

1. Mount .iso file. Click on “Setup.exe” file. Agree on terms and conditions and click on “Next” button.

2. Select the required features from the list and click “Install” button. It will take around 7.90 GB of space if all features are installed.

3. Setup will create “System Restore Point” before starting the installation process.

4. Once it is done, it will start installation process.

5. Between setup will ask you to restart the system. Click on “Restart” button to restart your system.

6. Setup will resume, once system is restarted.

7. Now installation will take some time. Around 20-30 minutes.

8. Once setup is completed, you can launch Visual studio.

Now work on Visual Studio from anywhere on any device with online services such as CloudDesktopOnline.com and CloudAppsPortal.com

Step By Step Installing Microsoft SQL Server 2012

1. Mount .iso file and click on setup.exe, you will see the following screen.

2. Click on “New SQL Server stand-alone installation or add features to an existing installation”, you will see the following screen.

3. Make sure, status of the each rule is “Passed” then click “Ok” to continue.

4. Next screen, you will be asked to enter product key. You can also try it by specifying a free edition from the checkbox.

5. Accept terms and condition by clicking the checkbox, then click on “Next” button.

6. Product updates screen will appear, you can skip scan if you want. It is optional.

7. On the “Install setup files” screen, click on “Install” button.

8. Then “Setup support Rules” screen will appear, it will check the rules and display result against it. It should be “Passed”. Warnings can be ignored. If it is failed, then solve the appropriate rule, by installing.

9. Now select the appropriate option from the radio button. Default is set to “SQL Server Feature installation”.

10. Here comes “Feature selection” screen. Select the required feature from the checkbox list and click on “Next” button.

11. “Installation rule” screen will check for rules (appropriate requirements)

12. Next comes the “Instance Configuration”, by default it’s “MYSQLSERVER”. You can change it to whatever you want.

13. “Disk Space Requirement” screen will display “Disk Usage Summary”

14. Now comes the “SQL Server Configuration Screen”. You can leave it as it. Default service settings are OK. If you want, you can set password for each service listed.

15. On “Database Engine Configuration”, set the authentication mode to “Mixed Mode (SQL Server + Windows Authentication)”. Set the password and click on the “Add Current User” button to add the current logged in user who will have unrestricted access to database engine. You can add “N” number of users or can remove users by clicking on “Add” or “Remove” button respectively.

16. From next screen, it will ask for service configuration settings, set it as per requirement else just keep them as it is.

17. Click “Next” on “Error Reporting” screen.

18. Once “Installation Configuration Rules” are validated, click on “Next” button.

19. Then you will see the “Summary” screen. Click “Install” button to continue.

20. Installation will take some time, depends upon the configuration of your computer. Generally it will take around 15-20 mins to finish.

21. Once the installation is completed, check the status of the each feature installed on your system. “Close” to finish.

Step By Step Installing Microsoft Office Professional Plus 2010

Step by step installation guide for MS Office Professional Plus 2010

1. Click on Setup.exe file, You will see following screen, accept the terms of agreement and click on “Continue” button.

2. On the second screen, you will be asked to choose the installation. If you click on “Install now” button, it will install almost everything. But if you want to customise your installation, click on “Customise” button.


3. From the following screen, select the packages which do you want to install.


4. Then from the next tab, choose a file location. It’s optional. It is recommended not to change it.


5. Next comes the User information. It is optional, enter it if you want.


6. Click on the “Install Now”, it will start the installation.



7. Click on “Close” button to finish the installation.