![]() ![]() I don't want to use a printer, but put the output to a file on the network. Connect a lab instrument to the network HardwareĪll,I have a lab instrument that only has a USB port to send his data to a printer.Epicor will tell you 10+ can't even run with that on but it can and will run fine until you hit about 3.8 gb used on the App Pool, at which point it will crash and complain about memory. Other than the good practice of doing the transactional backups is to make sure if you are running E10+ that in your IIS App Pool settings on your Application Server that you have 32 bit turned off. I've mistakenly had the log file reach 300 or so GB in a test environment and ended up just wiping it out because it would not merge in during the backup. If they are hitting that limit the main DB file must either be absolutely massive (my 6.81 GB is with a 180 GB main DB) OR they aren't doing any Transaction Log backups in which case I almost guarantee they will be unable to now as it will time out and fail when trying to merge into the main file. I have the same limit on mine (suspect it is just a default), run the Transaction Log backup every 10 minutes and my log is 6.8 GB - of which most is likely empty and due to expansion from previous version upgrades in Epicor. While I agree that Transaction Log backups should be being done to manage the size of the Log DB file I'm not sure that they are really hitting the limit listed there, having a SQL Log file hitting that limit at 2 TB would require a log file that hasn't been backed up in a long time. 3,145,728 Mb onĪnd if you have "FULL RECOVERY" on your database, enable transaction log backups every x minutes if you need to recover from a disaster. Your GL transactions are saturating your EpicoreLive_Log, which is the max limit size of 2097152 Mb Have you contacted your Epicor representative for their recommendations? This is another discussion subject where an answer in this forum will never be sufficient for everyone. ![]() There are many ways to try to estimate your database size requirements, no one method works for everyone.Īs to log file size - this depends on the type of recovery method used (Full, Simple, or other), database activity, and transaction log backup frequency. You may want to look at this link: estimating-disk-space-requirements-for-databases Opens a new window This will then reduce the number of times SQL has to automatically increase the database file size. If you think you can estimate your total database size requirements, sure, you can put that in as the 'Initial Size'. You do not do this MS SQL does this in the background. When this free space is consumed (by data or indexes or other),then SQL will automatically grow the database size by the value specified in the properties page we already looked at. The first database properties page you opened (when opening properties for a database) shows you that (on the General page). MS SQL Server databases always have some 'free space' in them. ![]()
0 Comments
Leave a Reply. |