These kinds of tasks are a little more complex because we have to take care of the objects that we'll move (or migrate) from Access to SQL Server. SQL Server has some tools and wizards that can help you, like the Enterprise Manager, Query Analyzer and others. SQL Server does not manage forms, so you only can move the other objects:
Table -> You must check the new data types and select the one that matches your original one.
Query -> Those could be converted in queries, views, or even stored procedures or triggers
Your VBA Code -> You can't use it in SQL Server, however you can try to develop stored procedures or triggers to accomplish the same task.
There's software that can help you to accomplish part of the move from Access 2000 to SQL Server 2000 easily. You can download it from this site:
Also there's a document that would be helpful to read:
For More Information
- What do you think about this answer? E-mail us at editor@searchDatabase.com with your feedback.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- The Best SQL Web Links
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Microsoft SQL Server Installation
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.