Below is all the error in the log when we are bulk loading into SQLServer. Username,Pwd,tablename and the Server Name seem to be fine as we could load it using an ODBC stage.Please advice.
SQL server OLEDB provider authorization failed.
Failed to establish datasource connection.
Issue with SQL Server Bulk Load
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 7
- Joined: Wed Feb 08, 2006 2:34 am
Re: Issue with SQL Server Bulk Load
Seems like a problem with installation OR license issue. I am not sure thoughthumsup9 wrote:Below is all the error in the log when we are bulk loading into SQLServer. Username,Pwd,tablename and the Server Name seem to be fine as we could load it using an ODBC stage.Please advice.
SQL server OLEDB provider authorization failed.
Failed to establish datasource connection.
-
- Participant
- Posts: 145
- Joined: Fri May 02, 2003 9:59 am
- Location: Seattle, Washington. USA
Re: Issue with SQL Server Bulk Load
I would double check your connection information since it does not look like you are connecting to the databases.
Shawn Ramsey
"It is a mistake to think you can solve any major problems just with potatoes."
-- Douglas Adams
"It is a mistake to think you can solve any major problems just with potatoes."
-- Douglas Adams
Other possibilities...
Howdy!
Some other things to check:
1. Make sure the OLEDB driver is registered properly
2. Make sure that the DSN is using the proper Ascential SQL Server Wire Protocol driver.
If you are sure you have access to the system, then these are my first suggestions.
Bestest!
Some other things to check:
1. Make sure the OLEDB driver is registered properly
2. Make sure that the DSN is using the proper Ascential SQL Server Wire Protocol driver.
If you are sure you have access to the system, then these are my first suggestions.
Bestest!
Bestest!
John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services
"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"
John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services
"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"
Response to private email to help others
Hi again,
I received a private email on this, but thought the response would be of benefit to others should this be their situation. Here is the text I was sent:
I believe you will need to use ODBC to do what you wish to do. As for loading 10 million rows at once, perhaps you should look at partitioning the job or running multiple instances of it at once. There a lots of posts out on the site giving you instructions on how to do it (plus I'm still figuring it out myself, so I would be a bad source )
Ken Bland has an entire framework methodology for doing stuff like this, so you may want to look at how his job control stuff works as this is part of it.
Hope that helps!
Bestest!
I received a private email on this, but thought the response would be of benefit to others should this be their situation. Here is the text I was sent:
Now that we know what the target system is, the problem becomes evident. The target is Unix based and you cannot use OLEDB to attach to Unix (all you guru's out there - if I've misstated this please correct me). Your only option here is ODBC (Bill Gates' revenge) or a third party driver that will act as a translation layer for OLEDB to Unix.Hi John
I am trying to set up an environment where my target DB would be a SQL Server. Basically its a Windows Unix based Environment where my source system is in main frames. We are basically trying to set up an environment and were debating about the target DB. Could you shed some light on the performance part of SQL Server and how it would act at huge volumes say around 10 million rows.
Thanks alot sir and all your help in this regard would be appreciated
regards,
Bhanu
I believe you will need to use ODBC to do what you wish to do. As for loading 10 million rows at once, perhaps you should look at partitioning the job or running multiple instances of it at once. There a lots of posts out on the site giving you instructions on how to do it (plus I'm still figuring it out myself, so I would be a bad source )
Ken Bland has an entire framework methodology for doing stuff like this, so you may want to look at how his job control stuff works as this is part of it.
Hope that helps!
Bestest!
Bestest!
John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services
"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"
John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services
"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"
A quick follow up to this...
It just dawned on me, MCDBA testing notwithstanding....
How is SQL Server running on Unix??
Do you actually mean that your server setup is as follows (trying to make sure I've understood your messages above):
Source system: Mainframe
DataStage Server: Server Edition running on Unix ???
Target system: Microsoft SQL Server running on Windows ???
If this is the case, then my statement above is true. If different, then I may need to restate...
Bestest!
John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services
"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"
John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services
"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"