Posted by Anns via SQLMonster.com on 10/02/95 11:53

SQL 2005 - SQL Server Managment Studio, thank you, when I said I was
currently learning I am learning unfortunately on 2000 b/c that is the study
material I bought and cannot afford to upgrade right now.

You are right with the SQL 2000 Enterprise edition, it is so user friendly
and that edition is all I know and still learning at best with that.

Yes, my company will be doing this on 2005 but for now, my learning is on
2000.
You see I work in a another department besides IT and between that job/baby
and small buisness, I am trying to get my DBA (2000) certification, I would
like the upgrade (2005) but do not have the funds to upgrade.
I have an opportunity to help with this conversion process and learn in
between, but I am trying to get a better grasp of this before sinking.

Does the 2005 Managment Studio look alot like Enterprise manager?
Answer:

Ms Access to SQL - I am assuming your answer would then be exporting/dts tool
from SQL to pull over all these db's?
Answer:


Erland, tell me once the db's are pull over to SQL, now I have Visual Studio
2005 software open - what steps are taken in this software to rebuilt the
user faces and then how is it then put on SHAREPOINT??????????
ANSWER:


Erland Sommarskog wrote:
>> 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.
>

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-general/200607/1

[Back to original message]