Connecting to mainframe from SQL Server 2000

Hi,
I'm taking data from mainframe and processing it using SQL Server
2000. Now I take data from mainframe as .txt file and loading it to
the sql server 2000. How can I connect SQL Server 2000 to mainframe to
get the data.
Thanks
ShafeekOne way is to ftp the file to the distributed environment such as a Windows
file server or on the SQL Server box and then use DTS or Bulk insert/bcp
utilities.
"Shafeek Khalidh" <itsprobablyme@.msn.com> wrote in message
news:f086c89e.0307110827.5936d7bb@.posting.google.com...
> Hi,
> I'm taking data from mainframe and processing it using SQL Server
> 2000. Now I take data from mainframe as .txt file and loading it to
> the sql server 2000. How can I connect SQL Server 2000 to mainframe to
> get the data.
> Thanks
> Shafeek|||Why don't you try Extended Stored Procedure.
Because you can use C to write DLL, you can do almost anything in it.
Include connect to mainframe, and get some data, certianly you can put it
into server if you want.
cheers
"Shafeek Khalidh" <itsprobablyme@.msn.com> wrote in message
news:f086c89e.0307110827.5936d7bb@.posting.google.com...
> Hi,
> I'm taking data from mainframe and processing it using SQL Server
> 2000. Now I take data from mainframe as .txt file and loading it to
> the sql server 2000. How can I connect SQL Server 2000 to mainframe to
> get the data.
> Thanks
> Shafeek

Connect to SSIS Service on machine "Servername" failed: Error loading type library/DLL

Got above error on clustered sql2k5 x86 when connect to SSIS, any solution?

Check the article on "How to: Configure Integration Services on a Cluster" @. http://msdn2.microsoft.com/en-us/library/ms345193.aspx

Thanks,
Loonysan

|||Thanks for the info, but it's not related to my problem. SSIS installation is fine, the issue is I got above error when register SSIS in SSMS on active node. I can register same SSIS remotely on passive node without error.

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

|||

I'm getting the same problem and they only solution I've found is to add the user to the local admin group of hte remote server which is obviously not the desired approach.

Did you every manage to resolve this?

thanks

|||

TSZ wrote:

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

Is it timing out? It may be a firewall issue, where you would have to have port 135 open between your server and you. Also, you'll want to make sure that your user is in a trusted domain to SSIS.

Brian

|||

Per J wrote:

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

I know it's a bit OT, but I have the same scenario, but was not able to install SSIS on a failover cluster.
Can you point me to the "Guide" that you used for installation?

Thanks|||

Re: Clustering SSIS, there's a great whitepaper on TechNet or I have a video that can be seen here on how to cluster SSIS (about 10 mins in length): http://www.jumpstarttv.com/Media.aspx?vid=36

Brian

|||I ran into the exact same problem. I found, however, that its not really a SSIS issue, but actually a problem with a DLL, or a registry value from the client tools that was either erased or overwritten with a different version. With that in mind I removed the client tools and reinstalled them and that solved the problem

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Got above error on clustered sql2k5 x86 when connect to SSIS, any solution?

Check the article on "How to: Configure Integration Services on a Cluster" @. http://msdn2.microsoft.com/en-us/library/ms345193.aspx

Thanks,
Loonysan

|||Thanks for the info, but it's not related to my problem. SSIS installation is fine, the issue is I got above error when register SSIS in SSMS on active node. I can register same SSIS remotely on passive node without error.

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

|||

I'm getting the same problem and they only solution I've found is to add the user to the local admin group of hte remote server which is obviously not the desired approach.

Did you every manage to resolve this?

thanks

|||

TSZ wrote:

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

Is it timing out? It may be a firewall issue, where you would have to have port 135 open between your server and you. Also, you'll want to make sure that your user is in a trusted domain to SSIS.

Brian

|||

Per J wrote:

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

I know it's a bit OT, but I have the same scenario, but was not able to install SSIS on a failover cluster.
Can you point me to the "Guide" that you used for installation?

Thanks|||

Re: Clustering SSIS, there's a great whitepaper on TechNet or I have a video that can be seen here on how to cluster SSIS (about 10 mins in length): http://www.jumpstarttv.com/Media.aspx?vid=36

Brian

|||I ran into the exact same problem. I found, however, that its not really a SSIS issue, but actually a problem with a DLL, or a registry value from the client tools that was either erased or overwritten with a different version. With that in mind I removed the client tools and reinstalled them and that solved the problem