Check Links Payables Transaction Logican File

[villica]

Hello everyone and Happy New year

I was wondering if anyone can help me figure out why the check links locks up on teh Payables transaction Logical File. I have let it run close to 12 to 15 hours and I often have to stop. Any suggestions what could be causing this.

villica

 

[VictoriaYudin]

Do you get any errors? Or do you just think it's locked up because it's taking such a long time? How large is your database? Are you running check links when other users are in the system? Have you tried running it directly on the server?

Victoria
Flexible Solutions, Inc.

 

[villica]

Hi Victoria

we ran on the server. There are times when we have let it run for over 3 days. The database is huge. Probably around 40 gb. not one is in the system when the process is running

villica

 

[VictoriaYudin]

40GB is definitely huge. How may years is that? If it's covering a lot of years, you may want to take a look at Company Archive by Professional Advantage so you can move some of the historical years off to a different company, thus making the main db smaller and speeding up a number of processes.

However in the meantime, the only thing I can think of is contacting support to see if they can help you with running check links directly in SQL. I am not 100% sure that is possible, but certainly worth asking, since you are not able to run it at all right now.

Victoria
Flexible Solutions, Inc.

 

[villica]

I am really not sure how many years that is. Can this table be purged.


villica

 

[VictoriaYudin]

Anything can be purged, but the question is whether something you need will suffer as a result.

Even with a huge database you should be able to run check links. Does the progress bar ever come up? Have you checked the Process Monitor to see if anything is happening? Have you tried creating a dexsql.log?



Victoria
Flexible Solutions, Inc.

 

[villica]

I have checked the monitor and it looks like is doing something. Is there a utiliy that can show what the check links is doing. Maybe there is bad tx somewhere so I was wondering if there is way to filter it out.


villica

 

[VictoriaYudin]

The only options are either SQL Profiler or the DEXSQL.log, but I have a feeling both are going to give you a lot more data than you bargained for and it would be very difficult to actually pick out a 'bad' transaction from there if there is one.

Victoria
Flexible Solutions, Inc.