cncjay
Well Known Member
Hey All,
We are in the testing phase of using SQLServer 2008R2 SP1 on Windows 2008 x64 platform.
Originally, we were/are on AS/400 for our backend database.
We have migrated our DV (TESTDTA & TESTCTL and Central objects) onto SQL server. We have a custom environment (SQL900) based off the PY900 pathcode where its data and control tables are also on the SQL server whereas the central objects still reside on AS/400. We'll move those along with all the PD databases as well as the system databases during our cutover weekend.
We have started to test to see how the system performance. The initial reaction has not been good. For example, when using P4210 - doing a simple lookup for a particular B/U - it is timing out or taking very long to provide results. Doing basic queries from the query analyzer is taking very long to return results. For example, the F47011, which has around 500,000 records, while the count statement comes back with the result very quickly, doing a select * from crpdta.F47011 is taking three to four minutes. I have also run the EXEC sp_updatestat command but it didn't help.
any tips/direction to start looking into would be fantastic.
regards,
We are in the testing phase of using SQLServer 2008R2 SP1 on Windows 2008 x64 platform.
Originally, we were/are on AS/400 for our backend database.
We have migrated our DV (TESTDTA & TESTCTL and Central objects) onto SQL server. We have a custom environment (SQL900) based off the PY900 pathcode where its data and control tables are also on the SQL server whereas the central objects still reside on AS/400. We'll move those along with all the PD databases as well as the system databases during our cutover weekend.
We have started to test to see how the system performance. The initial reaction has not been good. For example, when using P4210 - doing a simple lookup for a particular B/U - it is timing out or taking very long to provide results. Doing basic queries from the query analyzer is taking very long to return results. For example, the F47011, which has around 500,000 records, while the count statement comes back with the result very quickly, doing a select * from crpdta.F47011 is taking three to four minutes. I have also run the EXEC sp_updatestat command but it didn't help.
any tips/direction to start looking into would be fantastic.
regards,