I have a database server running Microsoft SQL Server 2012 SP4 where I am trying to run SSIS packages as jobs through the SQL Server Agent that connect to our IBM netezza server, but my SQL Server does not have the requisite provider (IBM Netezza OLEDB) to interface with Netezza. Our DBAs have told me to figure it out myself, which is normally not an issue, but resources online seem to be very thin on this subject; has anyone dealt with this before or know of a resource that would instruct a noob like me how to go about installing the provider?
I don’t know why, but the package containing ODBC,JDBC and OLEDB drivers from IBM can usually only be obtained by raising an IBM support ticket.
Personally I would run an ‘all-but-open-source’ policy On the client software, but I’m not IBM :)
Related
All, I'm very new to DBeaver. I've installed the Lite edition and am liking it for the most part. However, I'm missing many of the SQL Server administration bits that I'm used to seeing in SQL Server Management Studio such as SQL Server Agent Jobs, Security, etc. Am I just missing this option, do I need a version other than Lite, or is this just functionality that does not exist in DBeaver?
I have ssis software(Microsoft SQL Server 2017 Data Tools 15.9.2) installed on our machines. we are not able to see all schemas after connecting it to snowflake through odbc driver. although i am able to see all schemas on older version but due to some problem, we can't use it. do anyone can help me with this issue.
There is a new windows application to be developed in visual studio 2010. The Clients requested that the application should have a local database on each of their laptops and the database should be synchronized with the central server when they are connected to the office network. The central server is windows server 2003 and the Client PC is windows 2007. Please help me with the answers to the below questions
Which version of sql server can be installed in windows server 2003?
Methods of synchronization with sql server if MS Access is used as a local database. Is linking of access database to SQL Server is a two way synchronization?
Can sql express be used on local to be synchronized with SQl server using microsoft sync framework? If yes please let me know the version of SQL express and SQL Server to be installed.
Please let me know the Pros and cons of the above methods or any alternative solution. I have done a lot of research on this but cannot come to a conclusion. Kindly help.
Thanks,
Riya
Check the system requirements of each SQL edition you are eyeing to use, that should tell you if you can install it on Win 2003 or not.
Linking Access to SQL Server stores your data in SQL Server, not in the local Access Database
Yes, see:Tutorial: Synchronizing SQL Server and SQL Express
I tried enough searching for a tool in Ubuntu to connect to my remote SQL Server but in vain. Can someone please suggest me a tool (cross-platform) which helps me manage DB in remote SQL Server?
Any Java/JDBC based tool should work. Those that come to my mind are:
Squirrel
SQL Developer (from Oracle, not OpenSource but free)
SQL Developer (not from Oracle)
Execute Query
SQL Workbench/J
You can either use the free jTDS JDBC driver, or the one supplied by Microsoft.
In case you are using NetBeans as your IDE, you can use the database explorer there. All you need to do is to add the MS SQL driver that you can download from MS download center.
I need to create a linked server to a DB2 database on a mainframe. Has anyone done this successfully on a 64-bit version of SQL Server 2005? If so, which provider and settings were used?
It's important that the linked server work whether we are using a Windows authenticated account to login to SQL Server or a SQL Server login. It's also important that both the 4-part name and OPENQUERY query methods are functional. We have one set up on a SQL Server 2000 machine that works well, but it uses a provider that's not available for 64-bit SS 2005.
We had this same issue with a production system late last year (sept 2007) and the official word from our Microsoft contact was that they had a 64 bit oledb driver to connect to ASI/DB2 but it was in BETA at the time.
Not sure when it will be out of beta but that was the news as of last year.
We decided to move the production server onto a 32 bit machine since we were not comfortable using beta drivers on production systems.
I know this doesn't answer your question but it hopefully gives you some insight
What provider are you using for Sql 2000? I'm pretty sure MS has an x64 OLEDB driver for DB2 (part of Host Integration Server, but available as a separate download). IBM has x64 for .NET and ODBC, and possible OLEDB as well (though it's a PITA to find).
Once you get the linked server setup, I'm pretty sure all of your other requirements would be automatic....
From the Sql 2005 February 2007 Feature Pack:
The Microsoft OLE DB Provider for DB2 is a COM component for integrating vital data stored in IBM DB2 databases with new solutions based on Microsoft SQL Server 2005 Enterprise Edition and Developer Edition. SQL Server developers and administrators can use the provider with Integration Services, Analysis Services, Replication, Reporting Services, and Distributed Query Processor. Run the self-extracting download package to create an installation folder. The single setup program will install the provider and tools on x86, x64, and IA64 computers.