3

Goals - Automate exporting SQL Server 2005 views to Microsoft Access 2003 database (no transformation required) through SQL Server Job (with SSIS package)

There is no "Access DB Destination" in BI toolbox. So the question is,
How can I create an Access database (for me to load data to)?

dance2die
  • 1,961
  • 7
  • 31
  • 40

2 Answers2

2

There is an a destination for Access database, as long as the Access database already exist. You would add your SQL Server 2005 and the Access database to the connection manager. Then chose the OLE DB source and destination within your data flow. It will allow you to chose the Access connection as your destination.

Now if you are wanting to create the Access database on the fly, that is something different and would require a bit of scripting to accomplish.

Your Connection Manager properties and OLE DB destination editor for your access database would look similar to this: enter image description here enter image description here

0

I prefer to use the wizard to do this sort of thing.

Right-click the database, Tools, Export Data.

It will prompt for your data-source (your SQL Server database) and your data destination (choose either MS Access or ODBC for Access.)

I believe you can also use a data transformation task to do this. Drag on a source connection (SQL Server) and a destination connection (Access/ODBC) then join them with a transformation task. You won't actually do any transformations, but it still needs to know which field names match which in the source/destination table.

Note: ODBC functionality is not available in 64-bit Windows 2003 servers, as Microsoft helpfully removed the 64-bit ODBC DLL. It is coming back in 2008 due to overwhelming demand, apparently.

Andy Shellam
  • 1,828
  • 1
  • 12
  • 16
  • 1
    @Andy: I should have been more thorough in my question that I actually want to *automate* the process. By creating a SSIS package, I was thinking about creating a sql server job that runs weekly. – dance2die Feb 08 '10 at 20:02