how to handle huge amount of data in Sql Server

Question

1.00/5 (1 vote)

See more:

Hi all :)
I want to handle a very big data in SQL Server if any one know good technique kindly guide me.
the application run 24 hours on server and fetch protocols data from router in to database initially SQL Server is consist of one table within one hour the table contain more then millions of records due to large traffic load.
the table also consist of required indexing but after one day it is very hard to search in this table so what techniques should I used to control this amount of data.
Any Suggestion will be appreciated From seniors... :)

Posted 14-Jun-14 4:24am

Jawad Ahmed Tanoli

Add a Solution

Comments

PIEBALDconsult 14-Jun-14 11:25am

What sort of data? Do you have an example? I hope you're not trying to log data sent across the network.

Jawad Ahmed Tanoli 15-Jun-14 5:21am

the application capture protocols over the server and the table consist of CaptureTime,SourceHwAddress ,DestinationHwAddress,IPType,SourceAddress,DestinationAddress,protocol ,SourcePort ,DestinationPort,ProtocolReadAbleData.

Jörgen Andersson 15-Jun-14 15:28pm

What kind of data mining are you trying to do?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mehdi Gholam · Answer 1 · 2014-06-14T19:29:00

Solution 1

SQL server is not suited for this type of high volume/velocity data usage, you should look into using high performance nosql engines (or even text log files) for ingesting data and post processing of the data for the queries you want.

Posted 14-Jun-14 19:29pm

Mehdi Gholam

Comments

Jawad Ahmed Tanoli 15-Jun-14 5:23am

so if choose text files to store data then how should i determine the queries to retrieve data .