?
Solved

backup of access 2003 database to sql 2008 r2

Posted on 2013-05-09
3
Medium Priority
?
376 Views
Last Modified: 2016-02-11
Straight Import of a access 2003 databse into sql 2008 r2 is not working and errors on the third table import

Unhandled exception at 0x75b6b760 in DTSWizard.exe: 0xE0434352: 0xe0434352.


, as there are not many tables and this is a once off to start I have imported via excel.

however I need to start running a daily job to import to our sql 2008 r2 database, what do you recommend i am importing over a network.

Do you prefer a query to be done, instead of ssis jobs.
Has anyone experienced issues of automating an import of access 2003 database to sql 2008 r2.

Its a basic database and eventually it will be upgraded.
I just need to save it now on a daily basis
0
Comment
Question by:Amanda Walshaw
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 21
ID: 39154492
Are you validating the data before importing?

For example dates: Are you validating them to be sure they are within the limits of MS SQL Server?
0
 

Author Comment

by:Amanda Walshaw
ID: 39154656
its straight tables I have just used the built import function in SQL, I have imported via excel but I want to automate a job from access 2003 to sql database.
via ssis.
0
 
LVL 21

Accepted Solution

by:
Boyd (HiTechCoach) Trimmell, Microsoft Access MVP earned 1500 total points
ID: 39166043
... is not working and errors on the third table import

If you are  getting error there may be data issues.  For example Access (JET) can handle date that SQL Server can't. When importing this will cause errors.

The easiest way to get started with SSIS is, using Management Studio, right click on the database you want to import into, under Tasks, select Import data. This kicks off a wizard which is quite straight forward. At the end of the wizard, you have the option to save the package to the server or to a file. If you save it to a file, you can then create a job and set the step type to be Sql Server Integration Services Package. You can then configure the parts of your package and schedule the job as normal.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Phishing attempts can come in all forms, shapes and sizes. No matter how familiar you think you are with them, always remember to take extra precaution when opening an email with attachments or links.
Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening.  This article shows how to create and use them.
Using Microsoft Access, learn some simple rules for how to construct tables in a relational database. Split up all multi-value fields into single values: Split up fields that belong to other things into separate tables: Make sure that all record…
With Microsoft Access, learn how to start a database in different ways and produce different start-up actions allowing you to use a single database to perform multiple tasks. Specify a start-up form through options: Specify an Autoexec macro: Us…
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question