REDSHIFT OLEDB BI Alias provider

More
5 years 7 months ago #10911 by famc
famc created the topic: REDSHIFT OLEDB BI Alias provider
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.

Please Log in or Create an account to join the conversation.

More
5 years 7 months ago #10914 by Moderator
Moderator replied the topic: Re: REDSHIFT OLEDB BI Alias provider
Hi,
Are you using "SQL Server Import and Export Wizard"? Could you e-mail more details to Support?

Thank you!

Please Log in or Create an account to join the conversation.

More
5 years 3 weeks ago #12595 by createg
createg replied the topic: Re: REDSHIFT OLEDB BI Alias provider
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:

Please Log in or Create an account to join the conversation.

More
5 years 3 weeks ago #12599 by Moderator
Moderator replied the topic: Re: REDSHIFT OLEDB BI Alias provider
Main connection parameters can be specified in the "Connection" pane as shown. Additional parameters can be specified in the "All" pane.
Attachments:

Please Log in or Create an account to join the conversation.

More
5 years 1 day ago #12653 by TealCanady
TealCanady replied the topic: Re: REDSHIFT OLEDB BI Alias provider
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]

Please Log in or Create an account to join the conversation.

More
5 years 23 hours ago #12654 by Moderator
Moderator replied the topic: Re: REDSHIFT OLEDB BI Alias provider
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.

Please Log in or Create an account to join the conversation.

More
5 years 22 hours ago #12655 by TealCanady
TealCanady replied the topic: Re: REDSHIFT OLEDB BI Alias provider
I'll contact support! Thanks!

Please Log in or Create an account to join the conversation.

More
4 years 11 months ago #12675 by TealCanady
TealCanady replied the topic: Re: REDSHIFT OLEDB BI Alias provider
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

Please Log in or Create an account to join the conversation.

Time to create page: 0.073 seconds
Powered by Kunena Forum