Does querying a SQL server create a lot of load?

[Adam]

Hi All,

We have a SQL database at work which is specifically setup to report
from. As far as I'm aware this has nothing else on it apart from a
relational database.

The I.T provider has provided us with the reporting software called
Impromptu Cognos however I would rather use MS Access to query the
database.

I've been advised that this causes a lot of load on the server.

Is this correct or am I being fleeced ?

 

[Arvin Meyer]

Actually almost no load on the server, since Access/JET is a file server
based engine. The load will be on the network, and it will be greater with
improperly designed queries that don't use the indexes built into the tables
on the data engine. Fleeced isn't exactly the word for it ... more likely
"snowed by the semi-knowledgeable" is appropriate.

Cognos, will actually place more load on the server than Access, but any
decent server or network should be able to handle the load from either
without even "breathing heavy".
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Adam]

Thanks Arvin, thats the answer I was looking for! The I.T provider is
trying to sell us another SQL server again for us to report on using
Access, I believe they have a vested interest in telling us porkie pies
!

Have you used Cognos ? Is there anything factual on the net that I can
use as evidence to support my case, .i.e any figures that may use
server loads from Cognos vs. Access ?

Adam

 

[Arvin Meyer]

Again, Access uses the server only send files, not process the data. The
network is loaded to a greater extent because the file being sent is larger,
but the server is loaded less. I have not used Cognos, but it is essentially
a reporting tool (actually they offer several different ones) which uses a
database as a source for its data. I have yet to see a better reporting tool
than Access, in terms of speed and ease of use. I am sure that there are
tools which can do things that Access can't, but you need to find out
whether they do something that you need that Access can't do. The words
robust, scale, etc. are meaningless technospeak without a requirement
determination.

The proper way to analyze what tool to use is to determine your requirements
in an Excel list add columns for each tool you are considering. Check off
each cell for each product that fulfills the requirement. Include cost,
implementation time, and ROI in your list. It will easily become apparent
which tool to use. Anything else is nothing but hype.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access Downloads
http://www.datastrat.com
http://www.mvps.org/access