Showing posts with label datasource. Show all posts
Showing posts with label datasource. Show all posts

Tuesday, March 27, 2012

access datasource in script component

I'm trying to access a group of rows in a data source in my script component (transformation). Currently im using the connection manager in the script component, acquire the connection, and issue a query command to get the data. This will happen on every rows being pass to the script component from the data source. Is there a better way to access the a group of rows from the data source?

It depends what you want to do. Perhaps you could populate an in-memory store of the data to prevent the round-trip each time.

Are you sure that cannot be achieved with LOOKUP component?

-Jamie

Tuesday, March 20, 2012

Access 2003 Linked Tables update

Hello,

I am trying to update some SQL-linked tables in my Access database by repoiting the existing linked tables to a new datasource. The problem is, when I go to select the machine data source where the table sits, I get an error message saying the MS Jet Database can't find the object. This is because when Access creates the linked table, it replaces the period in the <schema>.<table_name> with an underscore. So when I go to update the links, it is essentially looking for the new table with the wrong file name.

I have about 80 linked tables to update and I haven't been able to figure a work-around. HELP PLEASE!

Cheers,

Josh

According to http://www.microsoft.com/technet/archive/office/office97/reskit/office97/027.mspx

Renaming Linked Tables

When Access links a remote table, it prefixes the default table owner ID of the SQL Server to each table name. The period separator between the owner ID and the table name is replaced by an underscore because periods in table names are not permitted by Access. Thus, the names of linked tables no longer correspond to the original table names in your MDB file. The simplest way to correct this is to rename your tables to their original names after linking.

Thursday, March 8, 2012

Abstract DTS

Hello
I have a DTS package that loads an Sql Server Database with data from MS
Access datasource. The package works fine but I want to be able to change
either the source or destination connection or both (for reuse purposes) and
still have the package run.
Note that regardless of the connection the schemas remain the same.
My problem is that the DTS task seems to use the full path to the db
including server. For instance locally a destination connection table might
be referenced as aaa.dbo.MyTable1 whereas if i try to point the connection
at another instance of the database on a different server the reference for
the connection might be bbb.dbo.MyTable1.
How do i abstract out the server name in eitheer/or both the
source/destination connection? I want to be able to load clients tables with
data by using the same DTS package and just changing the connection
properties.
Thanks
TMHi
Check out:
http://www.sqldts.com/default.aspx?201
Global variables can be passed from the command line.
John
"Toff McGowen" wrote:

> Hello
> I have a DTS package that loads an Sql Server Database with data from MS
> Access datasource. The package works fine but I want to be able to change
> either the source or destination connection or both (for reuse purposes) a
nd
> still have the package run.
> Note that regardless of the connection the schemas remain the same.
> My problem is that the DTS task seems to use the full path to the db
> including server. For instance locally a destination connection table migh
t
> be referenced as aaa.dbo.MyTable1 whereas if i try to point the connection
> at another instance of the database on a different server the reference fo
r
> the connection might be bbb.dbo.MyTable1.
> How do i abstract out the server name in eitheer/or both the
> source/destination connection? I want to be able to load clients tables wi
th
> data by using the same DTS package and just changing the connection
> properties.
> Thanks
> TM
>
>|||Excellent thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:85674B0C-13A0-481D-A7D3-241AD7824971@.microsoft.com...
> Hi
> Check out:
> http://www.sqldts.com/default.aspx?201
> Global variables can be passed from the command line.
> John
> "Toff McGowen" wrote:
>
change
and
might
connection
for
with