Best Database choice for a web service?

Question

0.00/5 (No votes)

See more:

, +

I am a CS student who is becoming a sophomore. Currently I am working as a summer intern and I need help. My supervisor is ok for me using this website because he is busy with his own work. So I am only doing trivial work.

I have a class library that has a web refrence of my web service I made.
He told me that this web service is going to be used alot.

So I made the web service and I needed it to retain it's information through OS refreshing the service. So I made an SQL server Database. He said he is worried that the SQL server Database might be the bottleneck of the program. He said, try to make it so we don't have to use a database. And he said something about memory.

So my question here is. Which is the best choice to use if I need something to be very fast and use the least amount of memory so the server don't crash.

SQL server Database? or
An embedded database engine (DBF.NET Link[^])? or
In-memory database (SQLite Link[^])

Posted 8-Jul-11 12:20pm

Member 8015046

Updated 8-Jul-11 12:24pm

v2

Add a Solution

Comments

TRK3 8-Jul-11 18:34pm

How much is "alot"? And what kind (how much) information needs to be retained?

Member 8015046 8-Jul-11 18:52pm

Millions or Billions, but I have resorted to do speed test for each one.

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)

Christian Graus · Accepted Answer · 2011-07-08T12:47:00

The only reason I can see for it to be a bottleneck is if you store big files in it and have a lot of users. I would expect SQL Server to outperform the other options you mention. If you keep your SQL simple, if you use SQL Server and have problems with it, you can move your DB to another type later and see how it performs.