Software Applications Programming Errors and solutions.

You can learn  Microsoft Paint and 3D paint faster after watching this video. I hope you will like share and subscribe this video to get more updates, English version video. Hindi Version Video.

Below clip will show you English basic grammar learning start from Tenses in Hindi language. I hope you will like share and subscribe this channel . To get more video in list visit below playlist. English basics and Grammar Learning online easy way in Hindi

SQL injection (SQLi) is a type of attack in which a hacker can take advantage of the insecure SQL query a web application makes to a database server (such as MySQL, Microsoft SQL Server and Oracle). It exploits weaknesses in a web application that are usually the result of poor development practices or mistakes. SQL injections are among the oldest, most prevalent and dangerous web application vulnerabilities. Since SQL injections affect web applications that make use of an SQL database, virtually every type of web application needs to pay attention to it. By abusing an SQL injection vulnerability, an attacker may be able to bypass a web application’s authentication and authorization mechanisms, retrieve the contents of an entire database, and even add, modify and delete records  in that database, impacting its data integrity.

Please like , share and subscribe to learn more about MS Word, PPT, Excel. 

Issue: I want to check out this error that didn't show me while using the SQL Server 2008 version and its sql server business intelligence studio to create packages. Currently in the company we have migrated to SQL Server 2017, but when trying to execute a package with the SQL Agent (jobs) I get this mistake. Thing that never happened before. Suggestions: 1.This problem is of incompatibility with packages version before. 2.having a different bit version of windows and sql server or SSIS (64/32) can present issues. Reinstall/upgrade to 64 if possible.

Issue : This error come  before when migrate data from oracle to SQL server using SSIS ? Error Column "Col1" cannot convert between unicode and non-unicode string data types Solution: The column is coming back as unicode and then either being loaded into a non-unicode (varchar) column in the table, or possibly set to output as non-unicode in the oracle source (or non-unicode to unicode). Try putting a data conversion component in the data flow between the source and destination, and set data_1 column to match the type and width of the target table/column.