"Alex Maghen" wrote:
| In SQL Server 2000 there was a feature for "upsizing" MS Access database
| files into SQL Server Databases. Is this still around in 2005? I can't
find
| it and BOY do I need it.
|
| Alex

"Dave Patrick" wrote:

> The feature is part of Access not SQL server. It is easy to do manually.
> Create the database manually, then right-click the DB and choose Task|Import
> Data, drill into your Access DB and import the tables. Once imported you can
> create a Database diagram since all constraints will now be handled by SQL
> server. (make sure you key all of the tables)
>
> Then create an ODBC file DSN for this database connection, then fire up the
> Access database and right-click in the 'Tables' window, choose Link Tables,
> choose ODBC Databases() and then choose the DSN you created and finally all
> of the tables you need to link.
>
> You'll want to rename the old tables to "tableName_old" then rename the
> linked tables removing the "dbo_" from the table names.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Alex Maghen" wrote:
> | In SQL Server 2000 there was a feature for "upsizing" MS Access database
> | files into SQL Server Databases. Is this still around in 2005? I can't
> find
> | it and BOY do I need it.
> |
> | Alex
>
>
>

"Dave Patrick" wrote:

> Does this clear it up?
>
> Create the database manually (on SQL Server 2005), then right-click the DB
> (on SQL Server 2005) and choose Task|Import Data, drill into your Access DB
> and import the tables. Once imported you can create a Database diagram (on
> SQL Server 2005) since all constraints will now be handled by SQL server.
> (make sure you key all of the tables)
>
> Then create an ODBC file DSN for this database connection (to SQL Server
> 2005), then fire up the Access database and right-click in the 'Tables'
> window, choose Link Tables, choose ODBC Databases() and then choose the DSN
> you created (to SQL Server 2005 database) and finally all of the tables you
> need to link.
>
> You'll want to rename the old tables to "tableName_old" then rename the
> linked tables removing the "dbo_" from the table names.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
>

"Alex Maghen" wrote:
| Thanks. Yeah, I get it jow.
|
| Alex

"Dave Patrick" wrote:

> Good to hear. You're welcome.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Alex Maghen" wrote:
> | Thanks. Yeah, I get it jow.
> |
> | Alex
>
>
>

"Rob" wrote:
> Dave,
>
> I have tried the method that you described to import an Access database
> and
> I keep getting the same error:
>
> Could not set up data flow connections.  The conection type OLEDB
> specified
> for connection manager (then I see what looks like a registry entry) is
> not
> recognized as a valid connection manager type.
>
> I have also tried creating a new Integrated Services Project and run the
> import from there.  I get the same error.  When I try to upsize in Access
> I
> get a report that says that the tables were not converted.
>
> Any suggestions?