Database size grow quickly

hi,
we are facing a problem with the datebase size wich are growing so fast (>150 Mo) compared to the installation and the volume of data we have.
we have ~ 15 infocube/ODS: 3 are configured with the full update method, 12 are delta updated.
have you any idea that can help us solve this problem?
Thank you.

If you are sure about PSA (is the first reason of uncontrolled grow).
Check how many request you have in the infocube and the average record per request. Probably you need the Compression of the InfoCube.
Records that had been uploaded with the same key may be contained in an InfoCube several times but with a different request ID. This differentiation is necessary to be able to delete single requests out of an InfoCube after they have been uploaded.
http://help.sap.com/saphelp_nw04/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/frameset.htm
Chack also the aggregates, but compression reduce also aggregates.
Reagrds,
Sergio

Similar Messages

Oracle 9i Lite database size growing

The database size on Oracle 9i Lite is increased.
If I extract data and recreate database with them, volume can be reduced at 5-10 of time.
Whether there are any other ways of reduction of the size? Some tools, or may be internal Java classes.

Can i create the database without using the sync or the create db. Or programatically how do i create the database Check out the client side APIs, examples can be found in the documentation, see WINCE (PocketPC) Developer's Guide.
RP.

Profile Manager backup size growing quickly

Over the past 2 weeks Profile Manager (or PostgreSQL) has been creating backup files at a very high rate (in total more than 800 backups since March 30th). Each of these backup files are 16.7 MB in size (by now more than 14GB in total) and have this format '000000010000000x000000nn' (with x a capital character and nn a hexdecimal sequential number). The location of the backups is: /Library/Server/ProfileManager/Data/backup.
Questions:
What purpose do these backups serve?
Is something wrong (since it only started 2 weeks ago)?
Can I stop it?
Can I delete older ones safely?
What changed recently on my server:
Installed Server 3.1 (March 22nd) and Server 3.1.1 (April 4th)
Renewed my server certificate (was about to expire April 25yj so warnings since March 26th or 27th)
I did make some changes to profiles March 22nd. Also enrolled a new device
Thanks for the help

The files are created by PostGreSQL and contain WAL (write-ahead-logging) data. It's still not clear why these files should be growing at more than 33 MB a day.
Why is there no snapshot of the database taken, past WAL files deleted and new ones started every day/week/month? Can I do this myself? I'm now wasting 16GB of storage as an inefficient backup for PostgreSQL.

Database mailbox grow quickly Exchange 2010 SP3

Hello.
Since we migrated from Exchange 2003 to
2010, the growth of our databse mailbox
is excessive. We have a total mailbox
size hovering around 75 GB and the size of
the database is 120 Gb.
Mailbox quotas are very
limited and 90% of users move emails
from mailbox to PST personal folders.
I get the impression that the space freed by removing
emails or move them to PST
is not claimed as White Space
and hence the excessive growth of
the DB.
I have seen that there is a fix to solve this
problem for versions prior to Exchange 2010
SP3 but the current version we have
implemented and it is with SP3.
Any idea to find out what is happening and
how to fix it?
Thanks in advance and best regards.
tzariksi

Hi.
I have reviewed the total size the mailboxes
and Dumpster with the following command:
Get-MailboxDatabase"MailboxDatabase"|Get-MailboxStatistics|SortTotalItemSize-desc|ftdisplayname,TotalItemSize,itemcount,TotalDeletedItemSize
The result is:
•Total Mailbox size(GB)->82,213
•Total Dumpster size(GB)->14,531
•Total ->97,344
The size of the DB using the command:
Get-MailboxDatabase-Status|Sort-ObjectDatabaseSize-Descending|Format-Table
Name,DatabaseSize,AvailableNewMailboxSpace
Is as follows:
Name
DatabaseSize                            AvailableNewMailboxSpace
MailboxDatabase         107.4 GB (115,302,531,072 bytes)        1.438 GB (1,544,486,912 bytes)
The actual disk size occupied
by the MailboxDatabase is->112GB
What else may be using the space in theMailboxDatabase?.
Thanks and regards.
Pedro.
tzariksi

Maximum Database size in exchange 2007

Hi Team,<o:p></o:p>
What is the maximum database size we can have in Exchange server 2007 SP3 RU8 standalone server.<o:p></o:p>
In our environment we have 1800 users hosted on the
exchange 2007 server with DB size(EDB file) of 1.61TB. What is the maximum size it can grow upto. Any response appreciated.
Thanks<o:p></o:p>
Srini<o:p></o:p>

Amit just beat me to posting Harold Wong's article! :-) Since you're currently on 1.61TB the artificial limit has already been adjust via the registry setting mentioned (the article mentioned 50GB though I've seen others mention 250GB). So the maximum limit
is 16TB, but whoever adjusted things to allow your current size may have set the artificial limit as something smaller, so you'd want to check the registry to see what it has been set to in your case.
I'd also echo the comments about database size. Depending on how you handle backups then they may also play a part. Since most backups work on the basis of backing up / restoring the entire database (obviously backing up changes rather than the whole thing
each time), then the event of you needing to restore it's much easier if you have smaller databases to deal with. Splitting your mailboxes across multiple stores will help minimise the time required before you can get some users online again in the case of
a total failure. Also, if you split your mailboxes across 5 databases and then have a problem (for instance corruption) on one of them, then only around 1/5 of your users are effected rather than all of them.

Rebuild Database did not reduce the database size

I just completed a rebuild database. The rebuild completed much quicker than anticipated and in the end the did not reduce in size.
This is my first rebuild and since original installation I have deleted a number of masters. From my understanding thumbnails and previews are not deleted when the master is deleted. In order to delete the thumbnails and previews the db must be rebuilt. Is this correct?
The db is over 31.1gb. The rebuild took approx 10 minutes and when completed the db size was still 31.1gb. There was a message during the rebuild that read "Recovering projects". I was expecting to see stats showing previews and thumbnails being generated in the activity window but don't see it. Has the db been rebuilt?
Thanks for any assistance.

Rebuilding the database is for disaster-recovery, not file maintenance. I certainly wouldn't do it unless something was fundamentally broken and the application didn't run.
"rebuilding" the database seems to do the following:
(1) remove the database file completely (not even to the trash, it destroys the database utterly)
(2) run through the plist files and reconstruct a brand-new database from them all
I checked this (on an empty library) using hard-links from the commandline, and step (1) above scared me sufficiently that I'd only rebuild the database as an absolute last resort.
Now, 31GB seems a lot for a database that only took 10 minutes to rebuild - are you sure you're not telling us the size of the library (to find the database size, right-click on the library and select view-package-contents, then open the 'Aperture.aplib' folder and find the size of the 'Library.apdb' file. That's the file you're changing when you 'rebuild database'.)
If you're telling us the size of the entire aperture library instead, then that size will be completely dominated by the master RAW files you've imported. I'd guess your library will be less than 10MB.
My understanding is that previews are deleted (since they're stored as separate files alongside the master image, if you look in the folder hierarchy), but thumbnails aren't. The thumbnails are aggregated together into one-file-per-project (presumably for speed of access), and I'd guess the space is reclaimed for future use, but the file doesn't get any smaller. That's a classic trade-off for speed-of-access, and users like us are normally very keen on things being fast
-=C=-

Mailbox Database Size/White Space Reduction in a DAG

I have several large databases in which I'm moving mailboxes off of in an attempt to prevent my LUNs from running out of disk space. As well, I have several mailboxes of users who have left the company. My questions are as follows:
1. When I run remove-mailbox -id "some mailbox" -permanent $true, the mailbox is deleted from Exchange relatively instantly. Will Exchange recoup the white space that is left behind after the mailbox has been deleted so that the
database shrinks in size? Or will it just start writing over the white space rather than growing the size of the database?
2. Perataining to mailboxes that have been moved, if "Keep Deleted Mailboxes for" is set to 4 days on the database that holds mailboxes that I'm moving off, will the database hold onto the mailbox (even though it has successfully been moved to
another database) for the duration of the "Keep Deleted Mailboxes for" setting? Or will the mailbox be hard deleted after the move completes successfully?
3. As part of Online Maintenance, will Exchange defrag a databse and decrease the white space, thereby shrinking the database size or will I have to take it offline to do that?
4. What are the procedures to perform an Offline Defrag of an Exchange Databse? How risky is this?

Hello,
To answer your questions:
1.   When and online database defrag completes a pass on the database it will reclaim this as whitespace in the database. It will not however reclaim space on the disk by shrinking the .edb file. An offline defrag is required for that.
2.   Moved mailbox will not be hard deleted until the 4 day retention period has past, unless you manually purge them using Remove-StoreMailbox.
3.   Related to the answer for number 1. Exchange will fill whitespace as mailboxes grow, but it will not reclaim disk space.
4.   In a DAG you will you need to dismount the mailbox database and run eseutil /d against the active database copy. This is a relatively low risk procedure, but requires databases to be offline thus interrupting mailbox access. It can also
take quite along time depending on the database size. The rate of defrag estimated by MS is 9 GB/hr. Here is a reference:
http://support.microsoft.com/kb/192185/en-us
For these types of situations my preference (If disk space allows) is to move all mailboxes to a fresh database then delete the database with excessive white space

Should We consider Temp Data Files While Estimating The Database Size

Hi,
The Database Size is sum of physical files like
Control file
redo log file
datafiles
temp files
so i want to know why are we considering the temp files..Because it's temporary. At one stage of database, temp size it could me more and at one stage it could be less.
So why consider the temp file???
Please share your views on it..
Thanks
Umesh

So, in essence the size of your datafiles is the size of your tablespaces?No. The size of the tablespace is the sum of the sizes of the datafiles in the tablespace --- i.e. the datafiles determine the tablespace size, not the other way round.
(Although when you CREATE or ALTER TABLESPACE, you specify the sizes of the datafiles that you want to belong to the tablespace).
the temporary tablespace has space allocated to it regardless of whether there are temporary tables in that tablespace or not.Two points here :
1. On most OSs the temporary tablespace tempfile is created as a "sparse" file. So, if you issue a CREATE TEMPORARY TABLESPACE TEMP TEMPFILE 'xyz.dbf' SIZE 1000M; and then did an "ls -l" at the OS level, "xyz.dbf' would appear to be only a few tens of KBs in size. The OS "grows" the file to 1000M as necessary.
When talking to your OS administrator ensure that you get 1000M (or the AUTOEXTEND MAXSIZE !!) space allocated even though he might "see" only a few 10s of KBs used on the first day.
2. The temporary tablespace does not have objects (other than "global temporary tables" that overflow from memory to disk). It is really temporary space for joins, sorts, order bys etc.
So, your datafile size is not affected regardless of your temporary tables coming and going.Yes, your datafile sizes and tempfile sizes are independent. Yet, when "sizing" disk space for the database you must include the tempfile size. However, when reporting to IT Management with a statement "our database size is ".. you might want to break it up into components like Data Dictionary, Tables, Indexes, TemporarySpace, RedoLogs and ArchiveLogs. You could also differentiate between OS-allocated space (sizes of datafiles) and Oracle-allocated space (sizes of segments) and actual used space (which you'd have to compute !) .
Hemant K Chitale
Edited by: Hemant K Chitale on Feb 17, 2011 10:42 PM
Added (Although ....) paragraph to first point.

How can we reduce compares Database size in express edition

Hi,
for client we use SQL server express edition. express edition has limitation of 10GB of database size.
please help me how can we reduce/compares DB size.
Regards,
Manish

Data or page compression feature is not available in express edition so you cannot use this feature to help you.
You might be lucky to reclaim space from shrink operation but eventually data file will grow again. So your best bet is using licensed version.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Database size history on Java instance

Hello,
Does anybody know how to get the database size history (db02) on a Java only instance.
The system is portal 7 running on SQL 2005 and windows 2003.
Thanks

Kruger,
Your best bet to get this type of information is going to be through the SQL Server Enterprise Manager. J2EE Engines typically do not grow as they rarely hold information but are pass-through systems. For this reason, there is little detail in the Portal for this specific type of information.
If you setup the Solution Manager as a CEN Monitor for the Java Instance you can provide some thresholds for the MTE's on Db but again, won't hold informaiton on size history.
Hope that helps - if this answers your question, please set this thread to answered.

Estimation of database size

Hi,
How can I estimate the database size required for a Netweaver system?
I am installing a new system with ESS and MSS.
And what is the rate that this database will normally grow?
Appreciate any reply.
Thanks,
Tzyy Ming

Hi Tzyy,
you should expect around 20 GB for a newly installed system. The growth rate very much depends on the scenarios you intend to use (MSS/ESS) and the number of users. Since it is almost impossible to predict the growth rate we always make sure that we provide enough space for at least 12 month under "worst case scenario" conditions - that works for us.
You might want to check the SAP Quicksizer (hardware estimate). It gives you an idea of what are relevant factors for your scenario: http://service.sap.com/quicksizing
Sven

Database Size Estimation

Is there a method available by which I can benchmark whether my database growth size is appropriate or not. As of now my database size is growing at an average of 20GB per month which I caonsider to be excessive. Please guide.

Hi Deepak,
You may want to understand first where the growth is from - which table space and which table? As mentioned by Markus, you can use DBA Cockpit to monitor your database. You can use the historical data in DBA Cockpit to see what's the delta change for tables/tablespaces and sort by the largest differences.
Have you also checked the High Water Mark (HWM) of the table spaces? If not you may need to use a combination of db2dart /rhwn or /lhwm and offline table REORG to reduce them(OSS Note 152531 and 486559). As update/insert/delete goes on, there is a lot of "holes" in the table spaces, these "holes" may make your table spaces bigger than it needs.
I hope it helps.
Regards,
-Beck

Database Size Incresing Fastly

In our Database ,Their only one master Table and 250 tables r logically connected to that master table.
Only master table contains Primary Kye.
So we are doing Indexing daily for faster performace.
Before some days database size is 10 gb and now it is 50 gb and the Database size is till incresing fastly.
I am not able to find out the problem that why database size incresing fastly.
And even i m not able find out logical connection between the table.
I have done shriking and re - indexing but still i m not able to resolve the problem.
How can i analyse that why database is incresing....
I m using SQL Server 2005.......
Thanks & Regards
Prash

I am not able to find out the problem that why database size incresing fastly.
And even i m not able find out logical connection between the table.
I have done shriking and re - indexing but still i m not able to resolve the problem.
How can i analyse that why database is incresing....You must understand your application first and then can find out what data is growing rapidly..
Bear in mind this is Oracle Database Forum. No MSSQL Questions.

Transaction Sync and Database Size

Hello,
We're using BDB (via the Java interface) as the persistent store for a messaging platform. In order to achieve high performance, the transactional operations are configured to not sync, i.e., TransactionConfig.setSync(false) . While we do achieve better performance, the size of the database does seem rather large. We checkpoint on a periodic basis, and each time we checkpoint, the size of the database grows, even though records (messages in our world) are being deleted. So, if I were to add, say 10000 records, delete all of them and then checkpoint, the size of the database would actually grow! In addition, the database file, while being large, is also very sparse - a 30GB file when compressed reduces in size to 0.5 GB.
We notice that if we configure our transactional operations to sync, the size is much smaller, and stays constant, i.e., if I were to insert and subsequently delete 10000 records into a database whose file is X MB, the size of the database file after the operations would be roughly X MB.
I understand that transaction logs are applied to the database when we checkpoint, but should I be configuring the behaviour of the checkpointing (via CheckpoinConfig )?
Also, I am checkpointing periodically from a separate thread. Does BDB itself spawn any threads for checkpointing?
Our environment is as follows:
RedHat EL 2.6.9-34.ELsmp
Java 1.5
BDB 4.5.20
Thanks much in advance,
Prashanth

Hi Prashanth,
If your delete load is high, your workload should benefit from setting the DB_REVSPLITOFF flag, which keeps around the structure of the btree regardless of records being deleted. The result should be less splits and merges, and is therefore better concurrency.
Here you can find some documentation that should help you:
Access method tuning: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/am_misc/tune.html
Transaction tuning: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/tune.html
If you are filling the cache with dirty pages, you can indeed call checkpoint() periodically in the application, or you can create a memp_trickle thread. See the following sections of the documentation:
- Javadoc: Environment -> trickleCacheWrite" http://www.oracle.com/technology/documentation/berkeley-db/db/java/com/sleepycat/db/Environment.html#trickleCacheWrite(int)
Some related thread for the "database size issue", can be found here: http://forums.oracle.com/forums/thread.jspa?threadID=534371&tstart=0
Bogdan Coman

Our database is growing-should I be concerned?

Our database is growing about 500 meg per day. I have provided graphicals of our production database and our test database which is a clone of production but was loaded some time ago.
The top chart is production: Our index is double the size of data-does that make sense and is it a design flaw?
The second is Test. It gets a tiny percentage of the use of production:
The index is considerably smaller.

Its hard to guess.
You can rely on sp_spaceused and see the difference.
The following query can tell you what data is scattered across different files. If you are running short of space why don't you add space as per the estimation.
https://technet.microsoft.com/en-us/library/ms189051%28v=sql.105%29.aspx
select
OBJECT_NAME(p.object_id) as my_table_name,
u.type_desc,
f.file_id,
f.name,
f.physical_name,
f.size,
f.max_size,
f.growth,
u.total_pages,
u.used_pages,
u.data_pages,
p.partition_id,
p.rows
from sys.allocation_units u
join sys.database_files f on u.data_space_id = f.data_space_id
join sys.partitions p on u.container_id = p.hobt_id
where
u.type in (1, 3)
--Prashanth

Database size grow quickly

Similar Messages

Maybe you are looking for