in one of our installation,

we have the SQL error reported frequently on table tfgld106
"the table object cross linked with another table object tdsls051."
"index corrupt".

while finalisation or while creating sequential dump etc..

temporarily we resolve it by re-organising it.

sometimes the table itself becomes not accessible from within baan;
it happens to other tables as well; like tdilc301, tdsls041 etc...

what to doubt:
Hardware
SQL installation
Harddisk

Baan says it is SQL problem
Microsoft checked and says it is not a SQL problem
IBM checked the hardware and says hardware is ok

what might be the problem.
the database size is around 90 GB; We are on SQL 2000 Standard and not enterprise. Is enterprise edition mandatory....

have u faced or any clues guys

thanks

VISH

I am sorry that I do not have ideas how to solve this. Where was the error reported?

In MSSQL 7.0 Standard Edition there was a limitation that baandb could not be greater than 10 GB. As far as I see you do have a larger database. Is there no such restriction on SQL 2000 ?

Can you please let us know if you managed to solve the problem?

hi guys,

we set the following things:

1) paging size
(virtual memory was wrongly set as 2GB; it was increased to 6GB)

2) concedentally users frequently complained lost connections with the server. While we checked Event Viwer too it was registered with lots of lost connections every now and then. Finally we removed a second network interface card and the lost connection problem is not there.

After these two things for the past one month we dont have the above SQL problem. I dont know how the above points have relation to this problem. But seem to have worked.

thanks guys

VISH

Do I see correctly that SQL complains about a link between tfgld106 and tdsls051? SQL should not be aware that these tables have a relation, So, I wonder if you or someone in your company made this relation. Can that cause this problem?

Hope this helps,
Dick