The Artima Developer Community
Articles | News | Weblogs | Books | Forums
Artima Forums | Articles | Weblogs | Java Answers | News
Sponsored Link •

C# Answers Forum
sql request vs memory work

1 reply on 1 page. Most recent reply: Dec 18, 2005 5:19 AM by Wasantha Wijayarathna

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 1 reply on 1 page
francois

Posts: 5
Nickname: cudenetf
Registered: Sep, 2005

sql request vs memory work Posted: Dec 8, 2005 4:21 AM
Reply to this message Reply
Advertisement
hi,
I have to make statistics about a sql table.
I can use many times some sql request using sum functions and so
or load the whole table in memory with a dataset and then make my "own business" there.
I'd like to know which solution is better and when one is better than the other (like how many sql request start to be too much to slow down significantly the program)

thanks


Wasantha Wijayarathna

Posts: 4
Nickname: wasu
Registered: Dec, 2005

Re: sql request vs memory work Posted: Dec 18, 2005 5:19 AM
Reply to this message Reply
Actually, options are depends on your requirements and the environment, for example if your data is very bulky it will be a problem to your memory to load all data in to the memory. If your data base is more costly (busy), number of connections to the datatbase should be minimized. There for you have to deside which method to be used. I think if you have lot of processing to be done on your data at and make the changes back to the database the Dataset is more usefull.

Flat View: This topic has 1 reply on 1 page
Topic: Doesn't VB come with .NET? Previous Topic   Next Topic Topic: first C++ .NET program
Sponsored Links


Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use