But what I have learnt from Mary Chipman who has been an MVP of both
products (she is now with Microsoft), is that you should not use the
wizard at all. There are so big differences between Access and SQL Server
that you cannot use a wizard and get a good result.
--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
You can use the wizard as a starting point, but tell it to only convert the
data structures and not move the data. Then you can make any
necessary/appropriate adjustments to the SQL data structures and then load
the data yourself. You can either use Access with a linked SQL Server table,
or use SQL Server Integration Services. Make sure you specify a primary key
for all the tables in SQL Server, because without one Access cannot copy
data to SQL Server.
What I would recommend is to create the data structures in SQL Server,
and then import the data. You can use SSIS if you need extensive data
type conversions. If you don't want to go the manual route, check out
SSMA for Access --
http://www.microsoft.com/sqlserver/2005/en/us/migration-access-learning.aspx.
It does more than the Upsizing Wizard, but you need to have an idea of
where you want to go with the data ahead of time so that you select
the correct options.
--Mary
On Mon, 14 Jun 2010 00:11:05 +0530, "S N" <uand...@invalid.com>
wrote:
"Mary Chipman [MSFT]" <mc...@online.microsoft.com> wrote in message
news:qvac169qlrnbu1hdr...@4ax.com...
--Mary
On Mon, 14 Jun 2010 22:58:20 +0530, "S N" <uand...@invalid.com>