|
|
Posted by Erland Sommarskog on 06/17/15 11:53
Anns via SQLMonster.com (u22580@uwe) writes:
> I work in Ms Access and intermediate at VBA and just learing SQL through
> the ENTERPRISE MANAGER SCREEN.
Enterprise Manager is a tool that exists only in SQL 2000, and I assume
- and hope! - that you will implement your new solution on SQL 2005. The
tool in SQL 2005 is SQL Server Management Studio which replaces both
Enterprise Manager and Query Analyzer. As long as you work with SQL 2000,
QA should be your main tool, because it is from this tool you most easily
can run queries. EM may look a little like Access, so you may feel com-
fortable with that. However, SQL Server is very different from Access,
so best is to use a tool that forces you to unlearn a lot things.
> I am just now looking at what Visual Studio 2005 is, but can some one
> tell me how this will all connect?
>
> What is the typical route for this process?
>
>
> Ms access to SQL - upsizing wizard or SQL importing?????
Yes, there is an upsizing wizard. And the word that I have from people
who have worked extensively with both Access and SQL Server is that you
should stay away from it. Access and SQL Server are very different and
build on different mindset. You should more or less redesign your
application for SQL Server and .Net. This may seem like a lot more work
that you had expected, but it is likely to pay off in the long run with
lower maintenance costs, if you do it right from the start.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|