Showing posts with label sql server. Show all posts
Showing posts with label sql server. Show all posts

Thursday, September 16, 2010

Neural Networks

The field of neural networks is wide, and the technological advances have made our lives simple. In my opinion, the neural network work field is abandoned by the world. It’s an area that only scientist, engineers and some other enthusiast take into account. During my student years, I had this fascination for this artificial intelligence division. In one occasion, I had to develop a project in which the work environment was crucial. The project consisted on a small car capable of recognize a determined type of terrain for crop development.

I was aware about what to do. however, something important was missing. A neural system needs to be properly trained. My next task was to develop software to train and design the neural network. In reality, this was not necessary, since there is a lot of functional neural network software in the market. To finish my Project, I had to buy software to develop and design the neural network of my car brain. At the end of the story, my project was a complete success. It was acquired by a local company dedicated to sell crop tools. Now, this device is manufactured as a crop inspection robot. Learning to design a neural network is crucial for our projects that require artificial intelligence technology. Therefore, I suggest acquiring all the equipment needed as books and software because in some way they make our life easy.

Friday, May 21, 2010

Server Configuration

Hi friends, as I was quite busy with work, I had no time to update ma blog. The issue was all about configuring a new server for our applications. Ah! It made me stay day and night at my desk. Since the applications are hosted over the internet, the server is heavily loaded and the applications are turning off now and then. As a result, 2 of the 14 applications are down everyday. So my manager thought of going in for a new dedicated server for some 5 major applications. The IIS configuration took a hell lot of my time. Similarly, installed VS 2008 (i.e) the .net team suite and then with the SQL server 2005. During the process, the credentials were wrongly given and we as a team did the SQL installation again. Work apart, enjoyed the days with team mates and felt like night shifts will do good than working on day shifts. So what's up with you guys? What's going on around? post me with updates. To be candid, I gained more knowledge on servers and other related stuffs. Though it was vellicating, it was good to work as a team thereby doing all the crazy pranks possible. Enjoyed a lot. Thanks a lot team. Oh God, server should work fine with no issues. Hoping for the best.

Friday, April 9, 2010

Difference between JOINS and UNION in SQL

In this post, I have given the difference between the use of Joins and the use of Union keyword in SQL.

I have a table named Table1 with Severity, Response SLA and Resolution SLA as its columns. Now I need to take the number of issues for both Response SLA and Resolution SLA based on Severity.

1. Using Inner join:

SELECT A.[Severity],A.[ResponseSLA],A.[Count],B.[ResolutionSLA],B.[Count] FROM
(
SELECT [Severity],[ResponseSLA], Count(1) As [Count] FROM Table1
WHERE GroupID = 4 AND [Month] = 'Mar - 2010'
GROUP BY [Severity],[ResponseSLA]
) A
INNER JOIN
(
SELECT [Severity],[ResolutionSLA], Count(1) As [Count] FROM Table1
WHERE GroupID = 4 AND [Month] = 'Mar - 2010'
GROUP BY [Severity],[ResolutionSLA]
) B
ON A.[Severity] = B.[Severity]
Order By A.[Severity]

The above query fetches the following result:

Severity

ResponseSLA

Count

ResolutionSLA

Count

Sev2

Not Met SLA

1

Not Met SLA

1

Sev3

Met SLA

29

Met SLA

31

Sev3

Not Met SLA

2

Met SLA

31

Sev4

Met SLA

597

Met SLA

613

Sev4

Not Met SLA

16

Met SLA

613


Note: You can replace "SELECT A.[Severity],A.[ResponseSLA],A.[Count],B.[ResolutionSLA],B.[Count] FROM" With "SELECT * FROM" and fetch all the columns.

2. Using Union:

Consider you need to calculate the total count. Then you should query as below.

SELECT * FROM
(
SELECT [Severity],[ResponseSLA], Count(1) As [Count] FROM Table1
WHERE GroupID = 4 AND [Month] = 'Mar - 2010'
GROUP BY [Severity],[ResponseSLA]
) A
UNION
(
SELECT 'Total' [Severity],'' [ResponseSLA], Count(1) As [Count] FROM Table1
WHERE GroupID = 4 AND [Month] = 'Mar - 2010'
)

The above query fetches the following result:

Severity

ResponseSLA

Count

Sev2

Not Met SLA

1

Sev3

Met SLA

29

Sev3

Not Met SLA

2

Sev4

Met SLA

597

Sev4

Not Met SLA

16

Total


645


Note: In UNION, the number of columns and the column names should match. In this case, the columns of both A & B should match each other.

Hope you understood the difference. Joins always add the columns to the left and the union statements add the columns to the bottom of the result grid.

UPI FRAUD - BEWARE List - 1

 People, Please DO NOT send money to the following UPIs. These are the fake people. Ramrr1008-1@okaxis Sonalisona444@apl Ayadav83195@okhdfcb...