Re: exporting to access
- From: jhofmeyr@xxxxxxxxxxxxxx
- Date: Tue, 8 Jan 2008 01:54:01 -0800 (PST)
Hi chris2383,
If you'd rather not provide any additional information, you could do
what Warren suggested above with some minor modifications:
1) Filter your data at the source. You do this by using a SQL
Statement in your OLE DB Source task inside your data flow. This is
the recommended method of using a OLE DB Source task anyway as a
custom SQL statement (even if it is simply "SELECT * FROM MyTable")
uses a more efficient connection to the one used by simply selecting a
table or view.
2) To export to Access your destination will need to be an OLE DB
destination using the Microsoft Jet 4.0 driver, the Excel destination
only allows exporting to an Excel file.
As a good starting point, try running the Export Data wizard from
inside SSMS and instead of choosing "Run immediately" at the last
step, choose to save the package (to the filesystem). Then open this
package in BIDS and have a look at what has been generated. This
should give you a basic feel for how SSIS packages are created.
Good luck!
J
.
- Follow-Ups:
- Re: exporting to access
- From: Warren Brunk
- Re: exporting to access
- References:
- Re: exporting to access
- From: Warren Brunk
- Re: exporting to access
- Prev by Date: RE: How to 'Keep Identity' On?
- Next by Date: Re: SSIS package will not run as a job step
- Previous by thread: Re: exporting to access
- Next by thread: Re: exporting to access
- Index(es):
Relevant Pages
|