E10 log files Blank Title 142382

Yahoo Archive
1
This is the best way I have found to truncate a log and get it smaller and keep it under control.

1- Set recovery mode to Simple.
2- Check how much of the log file is actually in use.
3- Run a backup, but set the backup to go to nul;Â BACKUP DATABASE EpicorERP10Â TO DISK = N'nul'
3- Set recovery mode to Full
4- Shrink the Log file of the DB to something smaller that you would likely handle your day to day log needs. 2-5GB usually handles it for most customers I work with.
5- Setup transaction log only backups mid day at slow points. This will back them up and truncate them.


On Wed, Jul 20, 2016 at 10:21 AM, Rob Bucek rbucek@... [vantage] <vantage@yahoogroups.com> wrote:
This really isn’t an Epicor issue, all SQL DB’s need maintenance, how much and how often depends on your usage, size, and other environmental variables. Fortunately, most if not all of the maintenance tasks can be put on a schedule and run in the background and do not require constant attention. Jose’s recommendation for Brent Ozar is a solid reference and has a lot of good information about database maintenance. MSDN, and stackoverflow.com can get you through shrinking and truncating your log file. If this is beyond the resources in your company, you may want to look to an outside resource for training and/or assistance with this.



Rob Bucek

Production Control Manager

D&S Manufacturing

301 E. Main St.

Black River Falls, WI 54615

715-284-5376 Ext. 311

Mobile: 715-896-3119

rbucek@...<mailto:rbucek@...>

Visit our newly redesigned Website at www.dsmfg.com<http://www.dsmfg.com/>



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]

Sent: Wednesday, July 20, 2016 8:58 AM

To: vantage@yahoogroups.com

Subject: RE: [Vantage] E10 log files







We already tried to 'shrink' them but didn't gain much space. Our DB is less than 1 GB but log file is 85GB (each database).



I've read a little bit so far about the log files needing to be truncated and a bit about checkpoints?



I am not a SQL DB administrator and we do not have one - we were very surprised by the amount of administration needed for this version. We just are coming off of Vantage 6.1 which required next to no administration.



We had a 3rd party install Epicor and had installed SQL per the install documentation - However, wondering if there was something missed such as needing to setup some backup plan for the SQL log files and checkpoints? Would this be considered part of Epicor install typically or maybe it was assumed this would be done after by someone? Would this be a normal part of SQL DB administration?



I think there were some good notes on this at last EMUG meeting but I haven't received the notes yet.



Any suggested practices or good links of a training video or documentation on this?







[Non-text portions of this message have been removed]



------------------------------------
Posted by: Rob Bucek <RBucek@...>
------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note:Â You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/links
------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
  http://groups.yahoo.com/group/vantage/

<*> Your email settings:
  Individual Email | Traditional

<*> To change settings online go to:
  http://groups.yahoo.com/group/vantage/join
  (Yahoo! ID required)

<*> To change settings via email:
  vantage-digest@yahoogroups.com
  vantage-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
  vantage-unsubscribe@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
  https://info.yahoo.com/legal/us/yahoo/utos/terms/


2

My transaction log files are enormous.  Tried to 'shrink' them but didn't gain much.  We were originaly at 10.0 and upgraded to 10.1.4 and then updated to 10.1.8


We have 5 databases, TRAIN, TEST, LIVE, PILOT, SANDBOX (restored backup of TEST) - as well as REPORT databases.  We have nothing but the GL structure in all but TRAIN and SANDBOX - so very small mdf files but the ldf files are over 80G  on a few of the databases.


Anyone know the cause and how to correct?  We have just about eaten up all our storage space and we are still in testing stage....


Is this normal type maintenance going forward?

3
The migration process does tend to grow those ldf files quite large. The use of Google will return a mountain of information on how to shrink your ldf file to a more reasonable size if space is a consideration for you. Ultimately the use of your system in its normal capacity will determine the optimal size of your ldf file and I’d leave it alone at that point. Once you are at 10.1 you shouldn’t need any specific maintenance to keep your ldf file in check other than proper backup practices.

Rob Bucek
Production Control Manager
D&S Manufacturing
301 E. Main St.
Black River Falls, WI 54615
715-284-5376 Ext. 311
Mobile: 715-896-3119
rbucek@...<mailto:rbucek@...>
Visit our newly redesigned Website at www.dsmfg.com<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, July 19, 2016 12:48 PM
To: vantage@yahoogroups.com
Subject: [Vantage] E10 log files



My transaction log files are enormous. Tried to 'shrink' them but didn't gain much. We were originaly at 10.0 and upgraded to 10.1.4 and then updated to 10.1.8



We have 5 databases, TRAIN, TEST, LIVE, PILOT, SANDBOX (restored backup of TEST) - as well as REPORT databases. We have nothing but the GL structure in all but TRAIN and SANDBOX - so very small mdf files but the ldf files are over 80G on a few of the databases.



Anyone know the cause and how to correct? We have just about eaten up all our storage space and we are still in testing stage....



Is this normal type maintenance going forward?



[Non-text portions of this message have been removed]
4
We already tried to 'shrink' them but didn't gain much space.  Our DB is less than 1 GB but log file is 85GB (each database).

I've read a little bit so far about the log files needing to be truncated and a bit about checkpoints?

I am not a SQL DB administrator and we do not have one - we were very surprised by the amount of administration needed for this version.  We just are coming off of Vantage 6.1 which required next to no administration.

We had a 3rd party install Epicor and had installed SQL per the install documentation - However, wondering if there was something missed such as needing to setup some backup plan for the SQL log files and checkpoints?  Would this be considered part of Epicor install typically or maybe it was assumed this would be done after by someone?  Would this be a normal part of SQL DB administration?

I think there were some good notes on this at last EMUG meeting but I haven't received the notes yet.

Any suggested practices or good links of a training video or documentation on this?

5
Your database is likely in Full Recovery Mode which is where it should be, however if you are not performing transaction log shipping or at least daily backups your logs are not being processed properly. You can set your database in Simple Recovery mode temporarily, truncate the logs and shrink it. Then put it back and ensure that the logs are backed up every single day.

Brent Ozar is a great place to get information here is an article on giant Transaction Logs

You said you don't have a DB Admin on staff.... you may not need one full time but you should hire someone to come in and setup your DB and maintenance plans correctly to ensure backups are happening right, re-indexes etc...




Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Wed, Jul 20, 2016 at 9:57 AM, parichter@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>We already tried to &#39;shrink&#39; them but didn&#39;t gain much space.  Our DB is less than 1 GB but log file is 85GB (each database).</p><div><br></div><div>I&#39;ve read a little bit so far about the log files needing to be truncated and a bit about checkpoints?</div><div><br></div><div>I am not a SQL DB administrator and we do not have one - we were very surprised by the amount of administration needed for this version.  We just are coming off of Vantage 6.1 which required next to no administration.</div><div><br></div><div>We had a 3rd party install Epicor and had installed SQL per the install documentation - However, wondering if there was something missed such as needing to setup some backup plan for the SQL log files and checkpoints?  Would this be considered part of Epicor install typically or maybe it was assumed this would be done after by someone?  Would this be a normal part of SQL DB administration?</div><div><br></div><div>I think there were some good notes on this at last EMUG meeting but I haven&#39;t received the notes yet.</div><div><br></div><div>Any suggested practices or good links of a training video or documentation on this?</div><div><br></div><p></p>

</div>
 


<div style="color:#fff;min-height:0;"></div>

6
For what its worth Progress did require maintenance also... though most people didn't do it. All DBMS's require maintenanceÂ


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Wed, Jul 20, 2016 at 10:13 AM, Jose Gomez <jose@...> wrote:
Your database is likely in Full Recovery Mode which is where it should be, however if you are not performing transaction log shipping or at least daily backups your logs are not being processed properly. You can set your database in Simple Recovery mode temporarily, truncate the logs and shrink it. Then put it back and ensure that the logs are backed up every single day.

Brent Ozar is a great place to get information here is an article on giant Transaction Logs

You said you don't have a DB Admin on staff.... you may not need one full time but you should hire someone to come in and setup your DB and maintenance plans correctly to ensure backups are happening right, re-indexes etc...




Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Wed, Jul 20, 2016 at 9:57 AM, parichter@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>We already tried to &#39;shrink&#39; them but didn&#39;t gain much space.  Our DB is less than 1 GB but log file is 85GB (each database).</p><div><br></div><div>I&#39;ve read a little bit so far about the log files needing to be truncated and a bit about checkpoints?</div><div><br></div><div>I am not a SQL DB administrator and we do not have one - we were very surprised by the amount of administration needed for this version.  We just are coming off of Vantage 6.1 which required next to no administration.</div><div><br></div><div>We had a 3rd party install Epicor and had installed SQL per the install documentation - However, wondering if there was something missed such as needing to setup some backup plan for the SQL log files and checkpoints?  Would this be considered part of Epicor install typically or maybe it was assumed this would be done after by someone?  Would this be a normal part of SQL DB administration?</div><div><br></div><div>I think there were some good notes on this at last EMUG meeting but I haven&#39;t received the notes yet.</div><div><br></div><div>Any suggested practices or good links of a training video or documentation on this?</div><div><br></div><p></p>

</div>
 


<div style="color:#fff;min-height:0;"></div>


7
This really isn’t an Epicor issue, all SQL DB’s need maintenance, how much and how often depends on your usage, size, and other environmental variables. Fortunately, most if not all of the maintenance tasks can be put on a schedule and run in the background and do not require constant attention. Jose’s recommendation for Brent Ozar is a solid reference and has a lot of good information about database maintenance. MSDN, and stackoverflow.com can get you through shrinking and truncating your log file. If this is beyond the resources in your company, you may want to look to an outside resource for training and/or assistance with this.

Rob Bucek
Production Control Manager
D&S Manufacturing
301 E. Main St.
Black River Falls, WI 54615
715-284-5376 Ext. 311
Mobile: 715-896-3119
rbucek@...<mailto:rbucek@...>
Visit our newly redesigned Website at www.dsmfg.com<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 20, 2016 8:58 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] E10 log files



We already tried to 'shrink' them but didn't gain much space. Our DB is less than 1 GB but log file is 85GB (each database).

I've read a little bit so far about the log files needing to be truncated and a bit about checkpoints?

I am not a SQL DB administrator and we do not have one - we were very surprised by the amount of administration needed for this version. We just are coming off of Vantage 6.1 which required next to no administration.

We had a 3rd party install Epicor and had installed SQL per the install documentation - However, wondering if there was something missed such as needing to setup some backup plan for the SQL log files and checkpoints? Would this be considered part of Epicor install typically or maybe it was assumed this would be done after by someone? Would this be a normal part of SQL DB administration?

I think there were some good notes on this at last EMUG meeting but I haven't received the notes yet.

Any suggested practices or good links of a training video or documentation on this?




[Non-text portions of this message have been removed]