Upsizing to SQL Server
Posted on 2006-03-20
Hello experts. Here is my situation. I have an existing business critical application that was originally built in Access2k as a file-system application. When I came on board, the application 'back-end'(tables) had been migrated to SQL Server2000. As far as I know, the tables were simply recreated in a new SQLServer database, and then the .mdb front-end linked to them via ODBC. There was no upsizing, no switch to .adp. Whoever did this simply created an .mde and distributed it. The performance issues are apparent. I mean there are forms that are retreiving 80,000+ records and access is filtering them on the front end.
I want to create a true client/server appliation here. I want to eliminate the front-end filtering. The user's biggest complaint is speed. Most of the documentation I've read is regarding upsizing stand-alone .mdb's with have local tables. However, my app is already using ODBC-linked to tables to SQLServer. And, its still using Access queries all over the forms. What would be some starting point suggestions. I am currently trying to upsize using the wizard. I have created a new database in SQL server(for this test-run upsize) and chose to create client server application(.adp). Am I heading in the right direction here?