<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "Derby size issue"]]></title>
		<link>http://www.sysaid.com/Sysforums/posts/list/112.page</link>
		<description><![CDATA[Latest messages posted in the topic "Derby size issue"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>Derby size issue</title>
				<description><![CDATA[ In order to reduce the size of the derby database, I have been going thru and removing attachments and/or SR's that we no longer need. After doing this and removing quite a large chunk of attachments, the size of the Derby database is still the same. Shouldn't the size of the database reduce if we delete a bunh of stuff?<br /> <br /> I read that there is no way to compact it, but I thought removing stuff would help.<br /> ]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/5852/25107.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/5852/25107.page</link>
				<pubDate><![CDATA[Fri, 12 Nov 2010 11:57:18]]> GMT</pubDate>
				<author><![CDATA[ venco]]></author>
			</item>
			<item>
				<title>Re:Derby size issue</title>
				<description><![CDATA[ The behaviour you have described is fairly typical of database files.  When you delete contents of the database file, the db file itself remains the same size.  <br /> <br /> In Microsoft databases the process is called a 'compact and repair'.  This would essential flush out that blank space that the database file is currently storing and reduce its overall size.  I didn't turn up any tools from a quick google that can perform this on a Derby database, but I am sure they exist.<br /> <br /> How big is your database?<br /> What is your concern with the size of the database.. i.e. Are you running out of disk space or do you feel its size could be the cause of a performance issue?<br /> <br /> If you feel Derby is not for you, SysAid is able to run on an SQL back end, however I haven't seen any instructions on how to set this up.  It might be a process that Ilient needs to be involved in to convert your database file.<br /> ]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/5852/25124.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/5852/25124.page</link>
				<pubDate><![CDATA[Sat, 13 Nov 2010 19:18:52]]> GMT</pubDate>
				<author><![CDATA[ SBIT]]></author>
			</item>
			<item>
				<title>Re:Derby size issue</title>
				<description><![CDATA[ I would love to run on SQL but that isn't an option at this time. After posting I did some tests and found the following:<br /> <br /> There are a couple of commands for Derby databases that seem to compact whatever table you want.:<br /> <br /> [b]SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE[/b](IN SCHEMANAME VARCHAR,IN TABLENAME VARCHAR,IN PURGE_ROWS SMALLINT,IN DEFRAGMENT_ROWS SMALLINT,	IN TRUNCATE_END SMALLINT )<br /> (<a class="snap_shots" href="http://db.apache.org/derby/docs/10.6/ref/rrefproceduresinplacecompress.html" target="_blank" rel="nofollow">http://db.apache.org/derby/docs/10.6/ref/rrefproceduresinplacecompress.html</a>)<br /> <br /> and <br /> <br /> [b]SYSCS_UTIL.SYSCS_COMPRESS_TABLE[/b] (IN SCHEMANAME VARCHAR, IN TABLENAME VARCHAR, IN SEQUENTIAL SMALLINT)<br /> (<a class="snap_shots" href="http://db.apache.org/derby/docs/10.6/ref/rrefaltertablecompress.html" target="_blank" rel="nofollow">http://db.apache.org/derby/docs/10.6/ref/rrefaltertablecompress.html</a>)<br /> [i]<br /> You have to have Auto Commit on to make it work it seems.[/i]<br /> <br /> I ran one of these on my sysaid database with all the proper parameters using a third party SQL program (like RazorSQL) after removing a bunch of the attachments I didn't need. It reduced the size by 700 MB or so which is just what I expected. Then I needed to test it to see if SysAid would still work and it seemed to work just find. All the attachments were removed from the SR's I wanted but the SR was still there. <br /> <br /> I was able to query the SysAid database to find the largest attachments by using a query like this:<br /> SELECT id, Length(file_content), file_name FROM SYSDBA.SERVICE_REQ_FILES;<br /> <br /> This showed me the SR#, the filename and the file size so I could sort by size and grab the largest ones.<br /> <br /> So I suppose that is one way to do it. I didn't have the guts to try it on my real database, but that may be coming.  <img src="http://www.sysaid.com/Sysforums/images/smilies/8a80c6485cd926be453217d59a84a888.gif" /> <br /> <br /> Matt]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/5852/25148.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/5852/25148.page</link>
				<pubDate><![CDATA[Mon, 15 Nov 2010 11:36:07]]> GMT</pubDate>
				<author><![CDATA[ savardm]]></author>
			</item>
	</channel>
</rss>