Skip to main content

What is difference between data profiling and query profiling

Data profiling
  1. Data profiling is the process of analyzing the source data to better understand, what is the condition of data.
  2. This task basically used in beginning of the development life cycle in OLAP or ETL application.
  3. So its related to OLAP and activities related to this process is data cleanings analysis, pattern analysis, number or nulls, aggregations, group , distinct values etc.
  4. Data Profiler is a tool available to do this.


Query profiling
  1. SQL Server or any database technology provides utility or tool that help to discovery query and slow running queries.
  2. Query profiling is related to OLTP applications. This helps to performance tunning and optimizations.
  3. We do analysis on index scan/seek, query IO/CPU/Memory usage , physical and logical reads etc.
  4. Profiler is the tool in SSMS to do this.


Comments

Popular posts from this blog

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription 

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.)    Creation of Application/Proxy user where Application is hosted. 2.)    Give appropriate access to the user. 3.)    Create Database Login user on database. 4.)    Authenticate User and provide credential on IIS. 5.)    Then Configure web.config on Application.