Monday, February 23, 2015

Weighted trust graph for authentication

During the hackathon (discussed in earlier post), I met with Gary.  He had come in to be play mentor, but since he couldn't devote enough time, ended up being a guest.

After engaging Neo4J in few meetups and understanding the database a bit, i was contemplating using Graph databases for authentication.  It might have consequent applications in fraud analytics too, where graph databases are used already[1]

During the discussion on the idea, Gary suggested to mould the idea differently and possibly using Trust networks/graphs, wherein each node (entities i.e. people, organisations etc) are related to each other through weighted directed relationships.  The weight of this relationship can be deduced in multiple ways, e.g. by periodic algorithms similar to search engine ranking algorithms or by asking people their trust level of others on a scale of 1 to x. x being a hypothetical standard scale that can be used as a yardstick across the network for determining level of trust.

While researching some more, I found that similar research has been done in this space [2], though applications are few to come by.

It was also pointed out in the discussion that banks don't really have a huge interest in preventing this crime.  the view was, since banks already provision for certain amount in their balance sheets for these "potential" thefts, they don't really bother so much.

I believe that the financial institutions as a single unit need to attack these fraud crimes by joining hands and leveraging best of research and technology for minimising the crime.  The technology exists for providing unto the moment information on these events, some more innovation and research is needed that can bring together the whole picture and look like a "solution"





[1]http://info.neotechnology.com/rs/neotechnology/images/Fraud%20Detection%20Using%20GraphDB%20-%202014.pdf?_ga=1.182367911.1656585956.1417700858
[2]http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.212.9978&rep=rep1&type=pdf

Tuesday, February 17, 2015

Hackathon - Fintechathon

A hackathon is a hacking marathon wherein many people are invited to attack problems around a theme.

I recently attended a hackathon over the valentines weekend.  Organised by StartupBootCamp Fintech, it was attended by about 100 people. Many ideas, many teams, some partners i.e. corporates with their own challenges.

I was initially team less, but then found some others who were in in my situation.  We formed a team,  around my favourite topic, data analytics.  We had two business development guys, Adam and Oksana, two java programmers, Nelson and Nick, and a mobile app developer Vlad.  

Hackathon teams are formed around ideas, wherein someone with an idea takes on the ownership, and the collects the team around it.  Things are focussed from moment one, and the march forward is fairly disciplined and fast, thats why the name hackathon... keep hacking, for long, long days and nights.

We, had the other way round.. all of us were teamless and therefore put together as a team. We had no idea to start with.  As a result of that, we spent better part of the friday evening and saturday zeroing on the problem to attack.  

Finally we decided to go ahead with an data analytics piece. I won't chalk out the details here, but its something that the marketing guys always love and like.  To know when their customers are off to a life event, and therefore could be offered some product.

By Sunday morning, we had lost two team members, one to a different idea and one to sleep. Vlad hadn't slept in 4 nights, so he kept sleeping much of Sunday.

As a result, we ended up a team without anyone who could do any UI design, and therefore only some backend API calls, some analytics pieces and nothing to show off.

The result was that, we couldn't show any working model in our pitch presentation and had to contend with a presentation only, which tried to describe our idea to the judges.

Of course we lost, but then it was a very nicely spent weekend, met some very nice people, made some contacts, and possibly a future for the idea.

Sunday, February 1, 2015

Playing with R

Since early 2013, when I got to know of possible online learning for R through www.coursera.com, I have been a fan of this language.

My teachers in college would probably not like to hear this, but I was never  a great Statistics student, it was always a "passing" requirement during my studies. However, when I learned about R and did some experimental work with R, i found that stats is indeed a very interesting and powerful mathematical tool. And with R i found it fun too, which in my personal opinion is the root of an ongoing learning process.  If learning is not fun, it stops.  

For me, laying my hands on RStudio was the best thing that happened to me around the statistics learning curve.  The tool makes your R learning curve so much more easy and possible, the college could never do that.

As an example, in college we could never realise real life examples and uses of regression, curve fitting etc.  However, now using R, it all makes so much more sense and with lot of ease. 

I can't put a finger on the clear reason, whether the years have added that capacity to understand the subject, or the very fact that today these kinds of tools exist which let you explore that area with so much straightforward ease, but the fact remains. It has become so much easy, relatively, to get your hands on the power of statistics and analytics with tools like.

Thats probably one reason, why i am getting more and more inclined towards data analytics. Its a very powerful and interesting area, with huge potential towards shaping our future.

Monday, May 26, 2014

Can we rollback the Truncate, Drop, and Delete command deleted data?

Here we talk about the concept of truncate, drop and delete commands and whether they can be rollback, if so, how and when !!

Yesterday I was working on this and see if we use the truncate command in transaction, we can rollback the data. One more thing if we perform delete command outside the transaction, we can’t rollback the data.

Let’s try this…

Suppose I have a table dbo.Employee with three column- Id, Name, and Salary.
CREATE TABLE [dbo].Employee(
      Id [int] NULL,
      Name [varchar](50) NULL,
      Salary [Int] NULL
)
Insert the values into the db.Employee table
INSERT INTO dbo.Employee VALUES(1,'Employee1',10000)
INSERT INTO dbo.Employee VALUES (2,'Employee2',20000)
INSERT INTO dbo.Employee VALUES (3,'Employee3',30000)
INSERT INTO dbo.Employee VALUES (4,'Employee4',10000)
INSERT INTO dbo.Employee VALUES (5,'Employee5',30000)
Now I have a five rows in table

SELECT * FROM dbo.Employee










Now we perform the delete command in Transaction and then select command
BEGIN TRAN
DELETE FROM dbo.Employee WHERE ID = 2
ROLLBACK

SELECT * FROM dbo.Employee
Output:

But again I run the select command then I get the same result as previous select statement (i.e 5).
Now I perform the Truncate command in Transaction, Let see what happen.
BEGIN TRAN
TRUNCATE TABLE dbo.Employee
ROLLBACK
Now again I run the select command and got the same rows and same result, if same thing we do with Drop command that will also give same result.
It means If we use the Delete, Truncate, and Drop command with Transaction, we can rollback the data and if we perform all three command outside the Transaction we can’t rollback.

One more thing I have to add in this article, we can’t rollback the data but we can restore the data from the Transaction_log, if we use the delete command. We can’t restore the data if we use the truncate or drop command. How and Why read in next article.

In summary, 
We can rollback the DDL and DML commands, if all these commands are in transaction. We can only restore the DML commands data. 

Thursday, May 22, 2014

Difference between Char, Varchar, and nVarchar data type in SQL Server



In real world everyone has different need and requirement, why we use the same data type to store different types of value. What is the actual difference between Char, Varchar and nVarchar data type.

Char DataType
Char datatype which is used to store the fixed length, non-unicode characters data. Suppose if we declared char (50) it will allocates memory for 50 characters. Once we declare char (50) and if we enter fewer than the number of characters defined (i.e. 6), the remaining length will be space filled to the right. it means other 44 characters of memory will be wasted.

Now we look in the query, How will it effect.

 

Output of this Select Statement:


Use this data type when the column data is to be of fixed length, which tends to be the case
for customer IDs and bank account IDs.

Nchar DataType
Nchar type is exactly similar to char. But hold character in Unicode format rather than ANSI. The Unicode format has a larger character set range than ANSI. Unicode datatype take exact double memory space in sql server. So use the nchar when you want to store the Unicode value.

varchar DataType

Varchar datatype, which is used to store the alphanumeric values, just like char datatype. If both are similar than what is the difference between char and Varchar? What is the need to create the new datatype? Later in this article we will discuss this. The maximum size of a Varchar column is 8,000 characters. However, if you define the column with no size—that is, Varchar () — then the length will default to 1.


Difference between the char and Varchar datatype

Char belongs to fixed length characters datatype, Varchar belongs to variable length characters datatype. If you define a column to be 20 characters long, but If you enter fewer than the number of characters defined like 10 characters then it will consume only 10 characters memory. It will not consume the defined memory.



Now we look in the query:





Output of the select statement:


We can see in above image the output of the select statement, the ZipCodelength value are varying according to data in zipCode field.


So we should use the Char for the fixed length data field and Varchar for the variable length data field.



Nvarchar DataType

Nvarchar datatype same as varchar datatype but only difference nvarchar is used to store Unicode characters and it allows you to store multiple languages in database. nvarchar datatype will take twice as much space to store extended set of characters as required by other languages.

Difference between Varchar and Nvarchar DataType
Varchar(n)
Nvarchar(n)
1.    Non-Unicode Variable Length character data type.



Example: Declare @FirstName As Varchar(20) = ‘Developer’

Select @FirstName



2.    It takes 1 byte per character.



Example: Declare @FirstName As Varchar(20) = ‘Developer’

Select @FirstName AS FirstName,

DATALENGTH(@FirstName) As Length



Result:

FirstName Length

Developer 9


3.    Can store maximum 8000 Non-Unicode characters.

4.    If the value of n is not specified at the time of variable declaration or column definition then it is considered as 1.

Example: Declare @FirstName As Varchar =’Developer’

SELECT @firstName FirstName,

DATALENGTH(@firstName) Length



Result:

FirstName Length

D                1

5.     If n is not specified in while using Cast/Convert   functions, then it is considered as 30.
     Example:
     Declare @firstName Varchar(50)=
‘Unicode character sets hold up to 65,536’
   
Select CAST(@firstName As Varchar) FirstName,
DATALENGTH(CAST(@firstName As varchar)) Length 
      Result:
FirstName                                Length
Unicode character sets hold up  30
1.    Unicode Variable Length character data type. Nvarchar  can store both the Unicode and non-Unicode (i.e) Chinese, Japanese, Korean etc) character.



Example: Declare @FirstName As Nvarchar(20) = ‘Developer’

Select @FirstName

2.    It takes exactly double bytes per character as compare to Varchar. It takes 2 bytes per Unicode/Non-Unicode character.



Example: Declare @FirstName As Nvarchar(20)= ‘Developer

Select @FirstName AS FirstName,

DATALENGTH(@FirstName) AS Length



Result:

FirstName Length

Developer 18

3.    Can store maximum 4000 Unicode/Non-Unicode characters.

4.    If the value of n is not specified at the time of variable declaration or column definition then it is considered as 1.

Example: Declare @FirstName As Nvarchar =’Developer’

SELECT @firstName FirstName,

DATALENGTH(@firstName) Length



Result:

FirstName Length

D                2

5.    If n is not specified in while using Cast/Convert     functions, then it is considered as 30.
      Example:
       Declare @firstName Nvarchar(50)=
 ‘Unicode character sets hold up to 65,536’
   
 Select CAST(@firstName As Nvarchar) FirstName,
 DATALENGTH(CAST(@firstName As Nvarchar)) Length
  
 Result:
 FirstName                                 Length
 Unicode character sets hold up   60 

    

So if you are not using other languages then it’s better to use varchar datatype instead of nvarchar.