Share
Report
191Microsoft Dynamics POS2009 uses the File Center for adding images, receipt formats etc. The image files are stored INSIDE the database rather than pointing to a file path outside the database.
Scenerio: I couple of months ago, a POS2009 database was created in SQL 2008 R2 Express SP1 upgraded from SQL 2008 Express in order to increase the database size limitation from 4GB to 8GB. I can verify that the database compatibility level is 100 and using the SQL 2008 R2 SP1 default instance: MSPOSINSTANCE_10.50. The database size is currently 4172.31MB. The log size is 50MB
The customer is stating they are still getting the error message that they are out of storage/memory on the register and can only continue to use the software once old images are deleted. I can not confirm the error in the Event Manager. The customer insists the database must still be contstrained by the previous 4GB data limit in SQL 2008 Express.
A script run against the database lists the sizes of the individual tables. The top two largest tables are as follows:
MasterPOSDB_Tombstone = 106970.971679 KB
Item = 38326.964840 KB
The POS Register is running Windows 7 Professional 64Bit, 1.05TB Hard Disk with 307GB Free Space, and 8GB of RAM.
POS2009 v.3.0 FP1, Binaries version: 3.00.1046.0.
I wonder if the problem is related to the SERVER's (MSPOSINSTANCE) Filestream properties? Filestream is disabled on the SERVER by default. I have researched SQL Filestream and understand there is a 2GB data limit, but since this is disabled, I am not convinced it's the problem.
Is there a limit to the table where the images are stored in the POS2009 database? Since the customer is using SQL 2008 R2 Express, there is no way to verify the maximum data size of a database without attaching a DB File greater than 10GB to verify how SQL Server responds.
*This post is locked for comments
All responses (
Answers (
