I upsized my Access .MDB file to work with SQL Server 2005 using the Upsizing
Wizard. After doing so, when I pull up the DB in Access, it shows the
original tables with the original spreadsheet-type icon, plus a new set of
tables with an arrow pointing to a globe-like green icon. I assume the globe
iconed tables are the new SQL tables and the spreadsheet ones are the
original unchanged ones, correct?
Also, I notice when I update the database with my Visual Studio project (I
updated the commands using OleDb... to SQL.., and updated the connection
string), apparently only the new globe-like tables are updated, and not the
old ones. Do I need to keep the original tables?
Also, I did a search on the hard drive and found a file with the new SQL
filename (the .mdb filename with SQL added on the end) in the folder Program
Files/Microsoft SQL Server/MSSQL.1/MSSQL/Data. To back up the new database,
what do I do--will backing up the .mdb file do it, or do I need to back up
the data file under the Program Files folder, or both? In other words, where
is the actual data being stored now?
Ed
Philipp Stiefel - 14 Nov 2005 07:57 GMT
<ewhite@newsgroups.nospam> wrote:
> I upsized my Access .MDB file to work with SQL Server 2005 using the Upsizing
> Wizard. After doing so, when I pull up the DB in Access, it shows the
> original tables with the original spreadsheet-type icon, plus a new set of
> tables with an arrow pointing to a globe-like green icon. I assume the globe
> iconed tables are the new SQL tables and the spreadsheet ones are the
> original unchanged ones, correct?
Yes, correct.
> Also, I notice when I update the database with my Visual Studio project (I
> updated the commands using OleDb... to SQL.., and updated the connection
> string), apparently only the new globe-like tables are updated, and not the
> old ones. Do I need to keep the original tables?
No, you don't. IIRC there is an option in the upsizing wizard
to keep the local tables instead of having them removed. I
guess you checked that option.
> Also, I did a search on the hard drive and found a file with the new SQL
> filename (the .mdb filename with SQL added on the end) in the folder Program
> Files/Microsoft SQL Server/MSSQL.1/MSSQL/Data. To back up the new database,
> what do I do--will backing up the .mdb file do it, or do I need to back up
> the data file under the Program Files folder, or both? In other words, where
> is the actual data being stored now?
To backup your data you'll need to backup the SQL-Server-Database.
If your database is in production and is used by several users, it
is highly recommended NOT to backup the file (the in the MSSQL\
Data-Path) but use SQL-Servers Backup&Restore features. By just
backing up the file you have no guarantee that the file is in a
consistent state and your backup may not work at all.
Cheers
Phil
penglinhui - 17 Dec 2005 07:41 GMT
"Ed White" <ewhite@newsgroups.nospam> дÈëÏûÏ¢ÐÂÎÅ:B4BCE413-B270-4679-AA0E-DA5D9D3AE71C@microsoft.com...
>I upsized my Access .MDB file to work with SQL Server 2005 using the
>Upsizing
[quoted text clipped - 21 lines]
> is the actual data being stored now?
> Ed
penglinhui - 17 Dec 2005 08:03 GMT
"Ed White" <ewhite@newsgroups.nospam> дÈëÏûÏ¢ÐÂÎÅ:B4BCE413-B270-4679-AA0E-DA5D9D3AE71C@microsoft.com...
>I upsized my Access .MDB file to work with SQL Server 2005 using the
>Upsizing
[quoted text clipped - 21 lines]
> is the actual data being stored now?
> Ed
penglinhui - 17 Dec 2005 08:06 GMT
"Ed White" <ewhite@newsgroups.nospam> дÈëÏûÏ¢ÐÂÎÅ:B4BCE413-B270-4679-AA0E-DA5D9D3AE71C@microsoft.com...
>I upsized my Access .MDB file to work with SQL Server 2005 using the
>Upsizing
[quoted text clipped - 21 lines]
> is the actual data being stored now?
> Ed