Hey there, IT folks,
Over the last 9 months, our database size has nearly quadrupled.
Would there be any way that just the creation of performances--with no transactions on them--could contribute unduly to use of space?
What would be the likely areas that would contribute most to such growth?
Thank you,
sharon,
Cincinnati Symphony
Hi Sharon, is it just your data or log file or both? Is there any chance that your database is in Full recovery mode and you are not taking Transaction Log backup regularly? In that case your log file size will grow enormously. Just for adding new performances it sounds too much.
Mo
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Sharon Grayton Sent: Wednesday, October 20, 2010 7:17 PM To: Mohiuddin Faruqe Subject: [Tessitura Technical Forum] DB growth
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
My DBA says we’re backing up transaction logs every 15 minutes.
Any other suggestions?
From: Mohiuddin Faruqe [mailto:bounce-mohiuddinfaruqe8297@tessituranetwork.com] Sent: Thursday, October 21, 2010 9:47 AM To: Sharon Grayton Subject: RE: [Tessitura Technical Forum] DB growth
In that case If you are worried about the Disk Space …Perform SHRINK DB TASK or SHRINK FILES TASK.
Don’t forget to take a backup…
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Sharon Grayton Sent: Thursday, October 21, 2010 10:39 AM To: Revanth Anne Subject: RE: [Tessitura Technical Forum] DB growth
Not knowing anything, my guess is T_CUST_DOC, which stores documents as blob image data. Here's a good way to know for sure, a short script that runs the sp_spaceused system proc on each table in the db.
CREATE TABLE #TEMP (name varchar(255), [rows] int, reserved varchar(255), [data] varchar(255), index_size varchar(255), unused varchar(255))
DECLARE @table_name varchar(255)
SET @table_name = (SELECT MIN(name) FROM sysobjects where type = 'U')
WHILE @table_name IS NOT NULL
BEGIN
INSERT #temp
EXEC sp_spaceused @table_name
SET @table_name = (SELECT MIN(name) FROM sysobjects where type = 'U' AND name > @table_name)
END
select * from #temp
GO
Thank you. I think we did figure out that it was the attached documents. They are being scanned much larger than they should be, so that what we thought was going in as 20-30K is actually at 1.5-2.5MB. That was a surprise.
From: Michael Reisman [mailto:bounce-michaelreisman4888@tessituranetwork.com] Sent: Thursday, October 21, 2010 2:24 PM To: Sharon Grayton Subject: RE: [Tessitura Technical Forum] DB growth
From: Revanth Anne <bounce-revanthanne9441@tessituranetwork.com> Sent: 10/21/2010 10:03:38 AM
Ok! To make it clear, the size / DPI of the scans are not to blame for the large size, it is the way Tessitura stores the file as an image data type. The images are actually IN the T_CUST_DOC.doc_contents column, not just as references to a location.
To editorialize for one second it would be a huge help to us if we could store compressed images in Tessitura and not have runaway database growth. Of course Tessitura was never intended to be a Document Management solution, so I'm sure many licensees are addressing (or, like me, planning to address) these needs separately.
Michael
Hi Sharon,
Good day.
there are a lot of different ways to control the db growth.
http://www.sqlskills.com/BLOGS/PAUL/post/Importance-of-proper-transaction-log-size-management.aspx
http://support.microsoft.com/kb/873235
have fun.
Ben