Article View: comp.databases.ms-sqlserver
Article #82Re: what is the impact of Database size on Performemce
From: Erland Sommarskog
Date: Tue, 30 Mar 2004 21:48
Date: Tue, 30 Mar 2004 21:48
37 lines
3169 bytes
3169 bytes
Avner (avnera@cvdo.com) writes: > I need some information to understand what is the impact of Database > size on the performemce. > > Few questions : > > 1. Is there any impact? Maybe. Maybe not. Depends whether you query the large table, and not the least how you query them, and what indexes you have. As a matter of fact, for the same amount of information, a database A twice as big as database B, could give better performance for retrieving a certain subset of that information, because in A data has been stored redudantly, maybe preaggregated. For instance, say that you have a transactions table for bank accounts, and you need to be able to retrieve the balance on a certain date. Saving the standings for each day is going to take up a lot of space, but it will be much faster to retrieve the historic balance, than adding up all transactions. > 2. Does one very large table impact the performence of the the whole DB, > meaning the overall performence and access the other tables. If the table just sits there, no. However, it will have an impact on backup operations. > 3. What are the ways to reduce the impact of the DB size on the DB > performence Good indexing is of course essential. -- Erland Sommarskog, SQL Server MVP, sommar@algonet.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Technical Details
Message-ID:
<Xns94BCF1DFDDA4CYazorman@127.0.0.1>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!newsrout1.ntli.net!news.ntli.net!news2.euro.net!amsnews01.chello.com!news01.chello.no!uio.no!uninett.no!news.algonet.se!algonet!news2.tninet.se!not-for-mailReferences:
<tSjac.16658$xb.714@newssvr27.news.prodigy.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f816f,2aea0b246c090747 X-Google-Attributes: gidf816f,public X-Google-Thread: 110f0d,2aea0b246c090747 X-Google-Attributes: gid110f0d,public X-Google-Thread: fa825,2aea0b246c090747 X-Google-Attributes: gidfa825,public X-Google-Thread: 104de1,2aea0b246c090747 X-Google-Attributes: gid104de1,public X-Google-Thread: ff490,2aea0b246c090747 X-Google-Attributes: gidff490,public X-Google-Thread: 107d2f,2aea0b246c090747 X-Google-Attributes: gid107d2f,public X-Google-ArrivalTime: 2004-03-30 13:46:37 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!newsrout1.ntli.net!news.ntli.net!news2.euro.net!amsnews01.chello.com!news01.chello.no!uio.no!uninett.no!news.algonet.se!algonet!news2.tninet.se!not-for-mail From: Erland Sommarskog <sommar@algonet.se> Newsgroups: comp.databases.ms-sqlserver,comp.databases.postgresql.admin,cz.comp.microsoft.sql,microsoft.public.il.hebrew.sqlserver,microsoft.public.sqlserver,microsoft.public.sqlserver.misc Subject: Re: what is the impact of Database size on Performemce Date: Tue, 30 Mar 2004 21:48:10 +0000 (UTC) Organization: Erland Sommarskog Lines: 37 Sender: sommar@algonet.invalid Message-ID: <Xns94BCF1DFDDA4CYazorman@127.0.0.1> References: <tSjac.16658$xb.714@newssvr27.news.prodigy.com> NNTP-Posting-Host: kairos.algonet.se Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: green.tninet.se 1080683290 10516 213.150.135.237 (30 Mar 2004 21:48:10 GMT) X-Complaints-To: abuse@telenordia.se NNTP-Posting-Date: Tue, 30 Mar 2004 21:48:10 +0000 (UTC) User-Agent: Xnews/06.07.17 Mime-proxy/1.4.c.0 (Win32) X-Received-Date: Tue, 30 Mar 2004 23:46:15 MET DST (news01.chello.no)