MartyConnelly
martyconnelly at shaw.ca
Thu Mar 16 15:15:44 CST 2006
Some notes and links for Upsizing to SQL 2000 and 2005 There is a problem which occurs when your Access database and the instance of SQL Server do not exist on the same computer. More so with Express because of TCP and firewalls. Avoid if possible. See blurb further down for fix on SQL 2000, and the Express forums post for SQL Express fix. How to use data transformation services (DTS) to export data from a Microsoft Access database to an SQL Server database http://support.microsoft.com/default.aspx?scid=kb;en-us;285829 Note: DTS is replaced in SQL 2005 by SSIS and is also not available for Express install. Access 2003 troubleshoot upsize wizard http://office.microsoft.com/en-us/assistance/HP030894261033.aspx http://office.microsoft.com/en-us/assistance/CH062526781033.aspx Access 2002 troubleshoot upsize wizard http://support.microsoft.com/kb/325019/EN-US/ Access 2003 Database Upgrade to SQL Server 2005 http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=128444&SiteID=1 Different Machine SQL 2000 upsize problem. This problem occurs when your Access database and the instance of SQL Server do not exist on the same computer. WORKAROUND To work around this problem, use a File DSN to connect to your instance of SQL Server when you upsize your Access database. To do this, follow these steps: Start Access. Open the problem database. On the Tools menu, point to Database Utilities, and then click Upsizing Wizard. In the Upsizing Wizard dialog box, click Use existing database, and then click Next. In the Select Data Source dialog box, select the appropriate DSN to connect to your instance of SQL Server on the File Data Source tab. Click OK. Enter the appropriate authentication information to connect to your instance of SQL Server if the SQL Server Login dialog box appears. Follow the instructions in the Upsizing Wizard. Notice that the Access database is successfully upsized without any errors. MORE INFORMATION Steps to reproduce the problem Start Access. Open the Northwind.mdb sample database. On the Tools menu, point to Database Utilities, and then click Upsizing Wizard. In the Upsizing Wizard dialog box, click Use existing database, and then click Next. In the Select Data Source dialog box, select the appropriate DSN to connect to your instance of SQL Server on the Machine Data Source tab. Click OK. Enter the appropriate authentication information to connect to your instance of SQL Server if the SQL Server Login dialog box appears. Notice that you receive the error messages that are mentioned in the "Symptoms" section, and you cannot continue the upsizing process. REFERENCES For more information about the Upsizing Wizard in Access 2003, click Microsoft Office Access Help on the Help menu, type About upsizing a Microsoft Access database in the Search for box in the Assistance pane, and then click Start searching to view the topic. For more information about the Upsizing Wizard in Access 2002, click Microsoft Access Help on the Help menu, type About upsizing a Microsoft Access database in the Office Assistant or the Answer Wizard, and then click Search to view the topic. For additional information about how to use the Upsizing Wizard in Access 2002, click the following article number to view the article in the Microsoft Knowledge Base: MSKB 330468 HOW TO: Use the Microsoft Access 2002 Upsizing Wizard For additional information about issues with the Upsizing Wizard in Access 2002, click the following article number to view the article in the Microsoft Knowledge Base: MSKB 328319 ACC2002: Issues with the Access 2002 Upsizing Wizard Shamil Salakhetdinov wrote: >Hi All, > >I'm getting this strange message from Upsizing wizard when MS SQL 2000 works >well and available from the other development tools and applications: > ><+ >Upsizing WIzard >[DBNETLIB] ConnectionOpen (Connect()).]SQL Server does not exist or access >denied. >-> > >Have anybody seen something like that? >Is there somewhere the sources of upsizing wizard to fix the problem? > >Yes, I think I enter security attibutes correctly in a login dialog shown by >upsizing wizard - I did try to use both Integrated Security and >UserName/Password - always fails with different databases, which are >available using the same DSN, e.g. to attach tables to MDBs or create ADPs >etc. > >Thank you. > >Shamil > > > -- Marty Connelly Victoria, B.C. Canada