Robert L. Stewart
rl_stewart at highstream.net
Wed Mar 24 12:57:54 CST 2004
Martin, Been there, done that. Make sure you use a number of file groups and that the tables are split between them. This will give you better performance because a thread is opened whenever SQL Server has to go to another file group for another table. Make sure you rename primary keys and indexes in SQL Server to whatever standard you setup. Use the Diagram tool to create "subject areas" so you can easily see relationships instead of having to navigate all the tables. Be ready to change the queries that you use to views to increase performance. Robert At 11:32 PM 3/23/2004 -0600, you wrote: >Date: Tue, 23 Mar 2004 21:58:02 -0000 >From: "Martin Reid" <mwp.reid at qub.ac.uk> >Subject: [AccessD] OT: Migration to SQL Server >To: "Access Developers discussion and problem solving" > <accessd at databaseadvisors.com> >Message-ID: <005101c41121$eaed9c10$1b02a8c0 at MARTINREID> >Content-Type: text/plain; charset="iso-8859-1" > >Anyone done any work migrating SEVERAL Access dbs to a single instance of >SQL Server?? > >Particulary interested in any problems this caused etc etc > >Maybe a pointer to things to come. I have been asked to look at several >areas around this subject including building .NET Front Ends to migrated >dbs. > >Martin