Reports timing out in conversion from Oracle to SQL server DB

 1 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
Margie Gyurisin
Veteran Member
Posts: 538
Veteran Member
    We are upgrading our Lawson applications from 900 to 901 and are moving from Oracle to SQL server as our DB. We are running into issues with converting our Crystal Reports and Access queries. Some of our Crystal Reports run for over an hour now without returning data - we usually kill them at that point. We have also been receiving errors like this - Databse Connector Errofr "42000:[microsoft][odbc sql server driver][swl server] The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databased [database vendor code:9002]' or "failed ODBC call, database timed out"

    Any ideas on how we can fix this?

    Thanks.
    John Henley
    Posts: 3353
      Off the top of my head, I'd say that it sounds like the indexes on the new database are missing/incomplete, and the queries are having to be sorted (i.e. into the temp space) in order to satisfy the report, which would fill up the temp space. Just a theory, but can you check the indexes on the new MSSQL database via verifymsf2000?

      Thanks for using the LawsonGuru.com forums!
      John