Enterprise Search eating up space

 You also need to back up the transaction logs.  This is the only way I could get the file to stop growing over time.


Tom



--- In vantage@yahoogroups.com, <jlisser@...> wrote:

These work like windows catalogs, sometimes they become corrupt and/or grow too large.  If the answer book Rob provided doesn't resolve, you can recreate the database and then rebuild it. From Epicor Admin Console, Enterprise Search Mgt select the server, delete the ES (SearchIndex900) database, then recreate it to reset it to the empty structure.  Next you right click the newly created database and select "Rebuild Index".  If you open a call with Epicor Technical Group they can send you the exact steps, I didn't see the answer book out there for this one but know they've walked me through it before.



--- In vantage@yahoogroups.com, <rbucek@...> wrote:

This is a more complete answer..




Summary: ES - SearchIndex900.ldf is very large; is there a way to reduce the size?

Book: Support Solutions

Page: 13347MPS



PAGE: 13347MPS



PROBLEM DESCRIPTION:

Enterprise Search log files SearchIndex900.ldf has grown very large (over 100GB). How can I stop the ldf from growing so it doesn't consume large amounts of disk space?



PROBLEM RESOLUTION:

The Enterprise Search database should be set to Simple recovery; every time you rebuild the index it completely recreates the data in this database so having the recovery level set to anything other Simple isn't necessary.



1. Launch SQL Server Management Studio on your SQL server.

2. Expand Databases node and right-click on SearchIndex900 database and select Properties.

3. Click on the Files page and set the Initial Size of the SearchIndex900_log to 5MB.

4. Click on the Options page and change the Recovery model to Simple - click OK.

5. Right-click on SearchIndex900 database select Tasks > Shrink > Database; click OK.



VERSIONS:

9.04

9.05


Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-4832
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:52 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space



The actual database. Our production DB is under 20GB.

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Monday, September 16, 2013 7:50 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space

Is it the DB that is that size or the log file? The Db should be relative in size to your production DB since it is just an indexed copy of certain tables and "views"

Josh

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Enterprise Search eating up space

I think this is related to ES. We have a database called SearchIndex900 and I think it is ES-related. It has grown to 45GB and nearly shut down the server this weekend. We cleared out some space but this seems strange. As a heads up, we haven't even really used ES at this point. It is installed, but we haven't exactly found a strong use for it. Any ideas on what is happening or what we might to do to get this under control?

Regards,

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

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



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

I think this is related to ES. We have a database called SearchIndex900 and I think it is ES-related. It has grown to 45GB and nearly shut down the server this weekend. We cleared out some space but this seems strange. As a heads up, we haven’t even really used ES at this point. It is installed, but we haven’t exactly found a strong use for it. Any ideas on what is happening or what we might to do to get this under control?

 

Regards,

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176

 

Is it the DB that is that size or the log file?  The Db should be relative in size to your production DB since it is just an indexed copy of certain tables and “views”

 

Josh

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Enterprise Search eating up space

 

 

I think this is related to ES. We have a database called SearchIndex900 and I think it is ES-related. It has grown to 45GB and nearly shut down the server this weekend. We cleared out some space but this seems strange. As a heads up, we haven’t even really used ES at this point. It is installed, but we haven’t exactly found a strong use for it. Any ideas on what is happening or what we might to do to get this under control?

 

Regards,

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176

 

The actual database. Our production DB is under 20GB.

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Monday, September 16, 2013 7:50 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space


Is it the DB that is that size or the log file? The Db should be relative in size to your production DB since it is just an indexed copy of certain tables and "views"

Josh

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Enterprise Search eating up space


I think this is related to ES. We have a database called SearchIndex900 and I think it is ES-related. It has grown to 45GB and nearly shut down the server this weekend. We cleared out some space but this seems strange. As a heads up, we haven't even really used ES at this point. It is installed, but we haven't exactly found a strong use for it. Any ideas on what is happening or what we might to do to get this under control?

Regards,

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176




[Non-text portions of this message have been removed]
Look at the log file settings in sql mgr, it should be set to simple.

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-4832
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Enterprise Search eating up space


I think this is related to ES. We have a database called SearchIndex900 and I think it is ES-related. It has grown to 45GB and nearly shut down the server this weekend. We cleared out some space but this seems strange. As a heads up, we haven't even really used ES at this point. It is installed, but we haven't exactly found a strong use for it. Any ideas on what is happening or what we might to do to get this under control?

Regards,

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176




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

I had an issue with the replication server. The log files grew out of control. Look in your Epicor Data Folder for 2 text files. If they are still growing, that’s your problem.

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 10:52 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space

 

 

The actual database. Our production DB is under 20GB.

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Monday, September 16, 2013 7:50 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space

Is it the DB that is that size or the log file? The Db should be relative in size to your production DB since it is just an indexed copy of certain tables and "views"

Josh

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Enterprise Search eating up space

I think this is related to ES. We have a database called SearchIndex900 and I think it is ES-related. It has grown to 45GB and nearly shut down the server this weekend. We cleared out some space but this seems strange. As a heads up, we haven't even really used ES at this point. It is installed, but we haven't exactly found a strong use for it. Any ideas on what is happening or what we might to do to get this under control?

Regards,

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

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

This is a more complete answer..




Summary: ES - SearchIndex900.ldf is very large; is there a way to reduce the size?

Book: Support Solutions

Page: 13347MPS



PAGE: 13347MPS



PROBLEM DESCRIPTION:

Enterprise Search log files SearchIndex900.ldf has grown very large (over 100GB). How can I stop the ldf from growing so it doesn't consume large amounts of disk space?



PROBLEM RESOLUTION:

The Enterprise Search database should be set to Simple recovery; every time you rebuild the index it completely recreates the data in this database so having the recovery level set to anything other Simple isn't necessary.



1. Launch SQL Server Management Studio on your SQL server.

2. Expand Databases node and right-click on SearchIndex900 database and select Properties.

3. Click on the Files page and set the Initial Size of the SearchIndex900_log to 5MB.

4. Click on the Options page and change the Recovery model to Simple - click OK.

5. Right-click on SearchIndex900 database select Tasks > Shrink > Database; click OK.



VERSIONS:

9.04

9.05


Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-4832
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:52 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space



The actual database. Our production DB is under 20GB.

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Monday, September 16, 2013 7:50 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space

Is it the DB that is that size or the log file? The Db should be relative in size to your production DB since it is just an indexed copy of certain tables and "views"

Josh

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Enterprise Search eating up space

I think this is related to ES. We have a database called SearchIndex900 and I think it is ES-related. It has grown to 45GB and nearly shut down the server this weekend. We cleared out some space but this seems strange. As a heads up, we haven't even really used ES at this point. It is installed, but we haven't exactly found a strong use for it. Any ideas on what is happening or what we might to do to get this under control?

Regards,

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

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



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

These work like windows catalogs, sometimes they become corrupt and/or grow too large.  If the answer book Rob provided doesn't resolve, you can recreate the database and then rebuild it. From Epicor Admin Console, Enterprise Search Mgt select the server, delete the ES (SearchIndex900) database, then recreate it to reset it to the empty structure.  Next you right click the newly created database and select "Rebuild Index".  If you open a call with Epicor Technical Group they can send you the exact steps, I didn't see the answer book out there for this one but know they've walked me through it before.



--- In vantage@yahoogroups.com, <rbucek@...> wrote:

This is a more complete answer..




Summary: ES - SearchIndex900.ldf is very large; is there a way to reduce the size?

Book: Support Solutions

Page: 13347MPS



PAGE: 13347MPS



PROBLEM DESCRIPTION:

Enterprise Search log files SearchIndex900.ldf has grown very large (over 100GB). How can I stop the ldf from growing so it doesn't consume large amounts of disk space?



PROBLEM RESOLUTION:

The Enterprise Search database should be set to Simple recovery; every time you rebuild the index it completely recreates the data in this database so having the recovery level set to anything other Simple isn't necessary.



1. Launch SQL Server Management Studio on your SQL server.

2. Expand Databases node and right-click on SearchIndex900 database and select Properties.

3. Click on the Files page and set the Initial Size of the SearchIndex900_log to 5MB.

4. Click on the Options page and change the Recovery model to Simple - click OK.

5. Right-click on SearchIndex900 database select Tasks > Shrink > Database; click OK.



VERSIONS:

9.04

9.05


Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-4832
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:52 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space



The actual database. Our production DB is under 20GB.

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Monday, September 16, 2013 7:50 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Enterprise Search eating up space

Is it the DB that is that size or the log file? The Db should be relative in size to your production DB since it is just an indexed copy of certain tables and "views"

Josh

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tom J. Christie
Sent: Monday, September 16, 2013 9:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Enterprise Search eating up space

I think this is related to ES. We have a database called SearchIndex900 and I think it is ES-related. It has grown to 45GB and nearly shut down the server this weekend. We cleared out some space but this seems strange. As a heads up, we haven't even really used ES at this point. It is installed, but we haven't exactly found a strong use for it. Any ideas on what is happening or what we might to do to get this under control?

Regards,

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

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



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