Anns via SQLMonster.com (u22580@uwe) writes:
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 can download the Evaluation Edition of SQL 2005 from
http://www.microsoft.com/downloads/d...A7F-C094-49A2-
A050-2D07993566EC&displaylang=en.
Even if your study material only covers SQL 2000, I still think you
should work with SQL 2005.
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.
Enterprise Manager != Enterprise Edition. Enterprise Manager is available
in all editions of SQL 2000, except for the desktop version MSDE. The
difference between the editions lies in what features that are available,
and what purpose the edition is licensed for.
Does the 2005 Managment Studio look alot like Enterprise manager?
It's not completely different, but there are also considerable differences.
In the end, you will only do yourself a disservice by learning a tool
that you will not work with.
But Enterprise Manager and SQL Server Management Studio are just the
tools. These are not what you should focus your learning on. You should
learn how to create databases, tables and indexes, and how to write
queries. You may think that you know SQL from Access, but as I said,
there are considerable differences. In general, SQL Server offers much
more powerful constructs, but there also features from Access that
are completely missing. A classic example is dynamic crosstabs.
Ms Access to SQL - I am assuming your answer would then be exporting/dts
tool from SQL to pull over all these db's?
Maybe. As I said, I think you should consider a major redesign, at
least in places where you have some quirks in Access, or in places
where SQL Server offers better solutions. Then again, even if you go
for a new schema, it may of course be a good idea bring over the
Access databases to SQL Server, so that you can work with them locally.
And for that end SQL Server Integration Services (which is the successor
to DTS in SQL 2005) may be a good choice. (I've never worked with
neither DTS nor SSIS, so I don't really know.)
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??????????
Since you are migrating from Access to .Net, I would assume that you
more or less rewrite the front-end code entirely, but you should ask in a
..Net forum about that.
Sharepoint? I know there is a product with that name, but I have very
little idea what it's good for. So I cannot answer that question.
--
Erland Sommarskog, SQL Server MVP,
es****@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx 
