REDSHIFT OLEDB BI Alias provider

Using PGNP with MS SQL Server, Data Transformation Services (DTS), SQL Server Integration Services (SSIS), Linked Servers, Snapshot and Transactional Replication and more.

REDSHIFT OLEDB BI Alias provider

Postby famc » Mon Mar 17, 2014 7:53 am

According to documentation, when using SSIS to import data BI Alias provider should be chosen. However, when I do that, there's no ability to configure connection to Redshift. The connection window looks like the one for SQL Server. Redshift Oledb provider (not BI Alias) doesn't have this problem.
famc
 
Posts: 1
Joined: Wed Mar 05, 2014 8:55 am

Re: REDSHIFT OLEDB BI Alias provider

Postby Moderator » Wed Mar 19, 2014 9:34 pm

Hi,
Are you using "SQL Server Import and Export Wizard"? Could you e-mail more details to Support?

Thank you!
User avatar
Moderator
Site Admin
 
Posts: 314
Joined: Wed Oct 29, 2008 11:27 pm

Re: REDSHIFT OLEDB BI Alias provider

Postby createg » Tue Oct 21, 2014 2:16 pm

Same issue here.

BIDS- SSIS

Connection manager- reg shift BI alias does not give the data links option or any details to configure the red shift connection.

The only available option is server name and sql server auth.

Attached picture
Attachments
Bi Alias.jpg
Bi Alias.jpg (81.86 KiB) Viewed 632 times
createg
 
Posts: 5
Joined: Thu Sep 11, 2014 11:32 pm

Re: REDSHIFT OLEDB BI Alias provider

Postby Moderator » Wed Oct 22, 2014 9:20 am

Main connection parameters can be specified in the "Connection" pane as shown. Additional parameters can be specified in the "All" pane.
Attachments
rsnpcxn.jpg
All pane
rsnpcxn.jpg (88.31 KiB) Viewed 625 times
rsnpcxn1.jpg
Connection pane
rsnpcxn1.jpg (74.69 KiB) Viewed 625 times
User avatar
Moderator
Site Admin
 
Posts: 314
Joined: Wed Oct 29, 2008 11:27 pm

Re: REDSHIFT OLEDB BI Alias provider

Postby TealCanady » Wed Nov 12, 2014 9:28 pm

I am experiencing a similar issue. I have added the parameters AWS_ACCESS_KEY=My_Access_Key;AWS_SECRET_KEY=My_Secret_Key; to the Extended properties in the BI Alias for RedShift.

Unfortunately it's not passing the key through in the Alias.

Is this a known issue? I just purchased this and am having an issue with the row by agonizing row involved when not using S3: ) Any help would be appreciated!

From PGNP profiler:

---------- Client SQL 2014/11/12 22:25:39.616 A03347BD ------------
COPY "dbo"."beaconresonate"("id","respondentid","rcid","rcount","timestamp") FROM 's3:///415E878EC282478197B5EBF2E1EAD476' CREDENTIALS 'aws_access_key_id=;aws_secret_access_key=' DELIMITER '|'
---------- Error ---------
ERROR: AWS access key ID not found
DETAIL:
-----------------------------------------------
error: AWS access key ID not found
code: 8001
context:
query: 5431087
location: aws_credentials_parser.cpp:96
process: padbmaster [pid=3821]
-----------------------------------------------
TealCanady
 
Posts: 3
Joined: Wed Nov 12, 2014 2:03 pm

Re: REDSHIFT OLEDB BI Alias provider

Postby Moderator » Thu Nov 13, 2014 6:39 am

Sorry, it was a bug. We fixed it, and prepared a new build. Please check for an official build (3304+), or contact Support to obtain the fixed module before the official release.
User avatar
Moderator
Site Admin
 
Posts: 314
Joined: Wed Oct 29, 2008 11:27 pm

Re: REDSHIFT OLEDB BI Alias provider

Postby TealCanady » Thu Nov 13, 2014 7:25 am

I'll contact support! Thanks!
TealCanady
 
Posts: 3
Joined: Wed Nov 12, 2014 2:03 pm

Re: REDSHIFT OLEDB BI Alias provider

Postby TealCanady » Sun Nov 23, 2014 8:57 am

Hey,

I received the new version which got me past the first error. Unfortunately I'm now receiving another error. It appears as though a GUID is being generated and appended to the bucket I'm trying to write to. Do you have any advice? The logged error is below from the profiler.

---------- Client SQL 2014/11/20 10:59:43.735 AD364D9C ------------
COPY "dbo"."beaconresonate"("respondentid","rcount","rcid","id","timestamp") FROM 's3://Teal//9E119D6BD7A44DEA9C5349622A894FE6'
CREDENTIALS 'aws_access_key_id=MyAccessKey;aws_secret_access_key=MySecretKey' DELIMITER '|'
---------- Error ---------
ERROR: The specified S3 prefix '/9E119D6BD7A44DEA9C5349622A894FE6' does not exist
DETAIL:
-----------------------------------------------
error: The specified S3 prefix '/9E119D6BD7A44DEA9C5349622A894FE6' does not exist
code: 8001
context:
query: 5578233
location: s3_utility.cpp:539
process: padbmaster [pid=18497]
-----------------------------------------------

Teal
TealCanady
 
Posts: 3
Joined: Wed Nov 12, 2014 2:03 pm


Return to SQL Server/DTS/SSIS/Linked servers/Replication

Who is online

Users browsing this forum: No registered users and 3 guests

cron